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
incorrectbehavior 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