Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xMuMA-00000002GRT-01pW for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2026 21:41:50 +0000 Received: from localhost ([127.0.0.1]:42986 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xMuM9-0000000CHPg-27og for pgsql-bugs@arkaria.postgresql.org; Fri, 30 Oct 2026 21:41:49 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]:50870) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xMuM9-0000000CHPY-16CY for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2026 21:41:49 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xMuM7-00000001l9x-1Okj for pgsql-bugs@lists.postgresql.org; Fri, 30 Oct 2026 21:41:48 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.18.1/8.18.1) with ESMTP id 69ULfkb42753559; Fri, 30 Oct 2026 17:41:46 -0400 DKIM-Filter: OpenDKIM Filter v2.11.0 sss.pgh.pa.us 69ULfkb42753559 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sss.pgh.pa.us; s=default; t=1793396506; bh=ZIXZ6rdfX5gkpvXzoM7jTH8RNjKybnzeAhrMwOw0bO0=; h=From:To:cc:Subject:In-reply-to:References:Date:From; b=CPhXPPX8PsW1KZZy5vUIBlBUlkG2F+PvQpM2BXm4+lIJjECjXtPCqGszMNWg3k0FE zhHMwS790m8Tv96gXCCHbYHiSIS9CSjrq7aZdpvrZONRkJkbKbZrNnK6rVgQLhKMzA KIwKe//IgAArts1rLkcyCuLWyp7Aeaw14JpW6dsc= From: Tom Lane 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 In-reply-to: <19809-c48ecb1edfc5f2d8@postgresql.org> References: <19809-c48ecb1edfc5f2d8@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Thu, 29 Oct 2026 06:26:24 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <2753557.1793396506.1@sss.pgh.pa.us> Date: Fri, 30 Oct 2026 17:41:46 -0400 Message-ID: <2753558.1793396506@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form 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