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