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

Richard Guo <guofenglinux@gmail.com>

From: Richard Guo <guofenglinux@gmail.com>

To: Stepan Neretin <slpmcf@gmail.com>

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

Date: 2025-07-28T08:20:45Z

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 Mon, Jul 28, 2025 at 3:39 PM Stepan Neretin <slpmcf@gmail.com> wrote:
> I tried to reproduce this issue on PostgreSQL 18beta2 (commit 3151c264) on Ubuntu 24.04, but I could not observe the incorrect behavior described.

> So the query still returns the expected row after the GiST index is created.
> If there are any additional settings or steps required to reproduce, please let me know.

You'll need to ensure that the plan uses an index scan.  Setting
enable_seqscan to off should be sufficient to do so.

Thanks
Richard