| From: | Richard Guo <guofenglinux(at)gmail(dot)com> |
|---|---|
| To: | Stepan Neretin <slpmcf(at)gmail(dot)com> |
| Cc: | exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Peter Eisentraut <peter(at)eisentraut(dot)org> |
| Subject: | Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops |
| Date: | 2025-07-28 08:20:45 |
| Message-ID: | CAMbWs49ucxae5_FfDDAPXuJYY1W2mQvz=BomPe62Mas_QR3FXQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Mon, Jul 28, 2025 at 3:39 PM Stepan Neretin <slpmcf(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2025-07-28 09:55:20 | Re: Unexpected Standby Shutdown on sync_replication_slots change |
| Previous Message | Stepan Neretin | 2025-07-28 06:38:54 | Re: BUG #19000: gist index returns inconsistent result with gist_inet_ops |