| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Guo <guofenglinux(at)gmail(dot)com> |
| Cc: | Julien Rouhaud <rjuju123(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Kyotaro HORIGUCHI <horiguchi(dot)kyotaro(at)lab(dot)ntt(dot)co(dot)jp> |
| Subject: | Re: Inconsistent results from seqscan and gist indexscan |
| Date: | 2021-11-27 02:51:51 |
| Message-ID: | 477813.1637981511@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Richard Guo <guofenglinux(at)gmail(dot)com> writes:
> On Fri, Nov 26, 2021 at 5:23 PM Julien Rouhaud <rjuju123(at)gmail(dot)com> wrote:
>> On Fri, Nov 26, 2021 at 2:10 PM Richard Guo <guofenglinux(at)gmail(dot)com>
>> wrote:
>>> Seems point_inside() does not handle NaN properly.
>> This is unfortunately a known issue, which was reported twice ([1] and
>> [2]) already. There's a patch proposed for it:
>> https://commitfest.postgresql.org/32/2710/ (adding Horiguchi-san in
>> Cc).
> Ah, I missed the previous threads. Good to know there is a patch fixing
> it.
Note that that patch seems pretty well stalled; if you'd like to
see it move forward, please pitch in and help review.
(Maybe we should scale back the patch's ambitions, and just try
to get the seqscan/indexscan inconsistency fixed.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2021-11-27 10:56:40 | Re: Skipping logical replication transactions on subscriber side |
| Previous Message | Tom Lane | 2021-11-27 02:46:55 | Re: WIP: WAL prefetch (another approach) |