| From: | shihao zhong <zhong950419(at)gmail(dot)com> |
|---|---|
| To: | John Naylor <johncnaylorls(at)gmail(dot)com> |
| Cc: | tomas(at)vondra(dot)me, heikki(dot)linnakangas(at)iki(dot)fi, manuelreyesbravo(at)gmail(dot)com, reshkekirill(at)gmail(dot)com, x4mmm(at)yandex-team(dot)ru, kehan5800(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19705: One NaN box makes a BRIN box_inclusion_ops index omit unrelated rows |
| Date: | 2026-10-01 03:04:19 |
| Message-ID: | CAGRkXqRbimqBSg9GYMGDSp7bpaDWed91Tyb6WHcr4Yw50bU8Rg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
> The following might be relevant as a different perspective:
>
> https://www.postgresql.org/message-id/1122078.1741378100@sss.pgh.pa.us
Hi John,
Thanks. I don't think v6 conflicts with Tom's idea. Banning NaN
would reject input that works today, so it can't be back-patched. And
in master, NaN boxes already on disk stay there after pg_upgrade. So
the indexes need fixing either way.
If you want less code, I can drop 0004 and use the v6-REL_18-0001
check on master too. That leaves no catalog change.
Thanks,
Shihao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ajin Cherian | 2026-10-01 03:09:19 | Re: BUG #19728: A logical replication apply worker segfaults dereferencing a NULL `MyLogicalRepWorker->stream_filese |
| Previous Message | David Rowley | 2026-10-01 02:22:44 | Re: BUG #19672: int8shl/int8shr Undefined Behavior on Out-of-Range Shift Amounts |