| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | 303677365(at)qq(dot)com |
| Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #19809: oidvector index dedup still returns wrong results on 18.6; CTAS persists the corrupted rows |
| Date: | 2026-10-30 21:41:46 |
| Message-ID: | 2753558.1793396506@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> Commit 882fd41 (2026-10-06, "Rescind unsafe deduplication support", fixes
> bug #19749) removed nbtree deduplication for bpchar but deliberately left
> oidvector_ops deduplication enabled on branches 14 through 18, to avoid
> making pg_amcheck report a corrupt metapage for
> pg_proc_proname_args_nsp_index. Its commit message reasons that "a user can
> only hit it by indexing an oidvector column that stores the output of a
> function like trim_array(). It seems very unlikely that any user would ever
> do that."
As per the previous discussion, we are not changing this in released
branches. Providing a reproducer for a case we already know exists
isn't moving the discussion forward usefully. The fact remains that
there's no good reason for user tables to contain oidvector columns.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2026-10-31 00:19:57 | Re: BUG #19821: pg_restore_attribute_stats() accepts an unsorted scalar histogram_bounds, producing badly wrong row |
| Previous Message | Tom Lane | 2026-10-30 21:36:52 | Re: BUG #19811: numeric log(base, x): wrong sign of Infinity result when base < 1; base 1 accepted with x = Infinity |