pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: 303677365@qq.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #19809: oidvector index dedup still returns wrong results on 18.6; CTAS persists the corrupted rows
Date: Fri, 30 Oct 2026 17:41:46 -0400
Message-ID: <2753558.1793396506@sss.pgh.pa.us> (raw)
In-Reply-To: <19809-c48ecb1edfc5f2d8@postgresql.org>
References: <19809-c48ecb1edfc5f2d8@postgresql.org>

PG Bug reporting form <noreply@postgresql.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






view thread (2+ messages)

Message-ID: <2753558.1793396506@sss.pgh.pa.us>
Permalink:  ../2753558.1793396506@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/2753558.1793396506@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, 303677365@qq.com
  Subject: Re: BUG #19809: oidvector index dedup still returns wrong results on 18.6; CTAS persists the corrupted rows
  In-Reply-To: <2753558.1793396506@sss.pgh.pa.us>
  References: <19809-c48ecb1edfc5f2d8@postgresql.org> <2753558.1793396506@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox