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.94.2) (envelope-from ) id 1r5ohH-00FD09-67 for pgsql-general@arkaria.postgresql.org; Wed, 22 Nov 2023 14:59:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1r5ohE-009P2Z-Rw for pgsql-general@arkaria.postgresql.org; Wed, 22 Nov 2023 14:59:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5ohE-009P2R-Aw for pgsql-general@lists.postgresql.org; Wed, 22 Nov 2023 14:59:20 +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.94.2) (envelope-from ) id 1r5oh7-006p8I-Md for pgsql-general@lists.postgresql.org; Wed, 22 Nov 2023 14:59:19 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 3AMEx7Dw1674347; Wed, 22 Nov 2023 09:59:07 -0500 From: Tom Lane To: CG cc: "pgsql-general@lists.postgresql.org" , Achilleas Mantzios Subject: Re: Removing oids with pg_repack In-reply-to: <1411824597.3692573.1700658864193@mail.yahoo.com> References: <1375662821.3508272.1700592084461.ref@mail.yahoo.com> <1375662821.3508272.1700592084461@mail.yahoo.com> <164bcbcf-73a5-4c8c-9016-7a185584d96e@cloud.gatewaynet.com> <1411824597.3692573.1700658864193@mail.yahoo.com> Comments: In-reply-to CG message dated "Wed, 22 Nov 2023 13:14:24 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1674345.1700665147.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Wed, 22 Nov 2023 09:59:07 -0500 Message-ID: <1674346.1700665147@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk CG writes: > I have the fallback position for the Percona ETL strategy. But I feel li= ke I'm REALLY close with pg_repack and I just don't understand enough abou= t the system internals to nudge it to correctness and need some expert ass= istance to tap it in the hole. The only "system metadata" that would need changing is pg_class.relhasoids. However, it's certainly necessary to rewrite all the physical table rows (and hence all the table's indexes). I don't know a lot about pg_repack, but I'm a bit skeptical that it can really make that transparent. I'm even more skeptical that it could almost support it except this obvious use-case never occurred to the developers. I suspect that either the support already exists but you missed it, or else there's some fundamental stumbling block. Maybe go discuss this with the pg_repack developers? (Maybe they read pgsql-general, but I wouldn't count on it.) regards, tom lane