Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops

Richard Guo <guofenglinux@gmail.com>

From: Richard Guo <guofenglinux@gmail.com>

To: Tom Lane <tgl@sss.pgh.pa.us>

Cc: Peter Eisentraut <peter@eisentraut.org>, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org

Date: 2025-08-01T02:38:31Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

ecpg: Fix memory leaks in ecpg_auto_prepare()
- 3151c264d460 19 (unreleased) cited

On Fri, Aug 1, 2025 at 3:17 AM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> We've known about this for, um, decades: btree_gist's support for
> inet/cidr is fundamentally broken [1][2].  It's still there
> only because nobody's been able to think of a way of removing it
> without causing pain for anyone who has indexes like that.
> But maybe we should just accept that it's going to cause pain
> and remove it.

I think correctness should take priority over avoiding pain.

Thanks
Richard