pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: CG <cgg007@yahoo.com>
Cc: pgsql-general@lists.postgresql.org <pgsql-general@lists.postgresql.org>
Cc: Achilleas Mantzios <a.mantzios@cloud.gatewaynet.com>
Subject: Re: Removing oids with pg_repack
Date: Wed, 22 Nov 2023 09:59:07 -0500
Message-ID: <1674346.1700665147@sss.pgh.pa.us> (raw)
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>

CG <cgg007@yahoo.com> writes:
> I have the fallback position for the Percona ETL strategy. But I feel like I'm REALLY close with pg_repack and I just don't understand enough about the system internals to nudge it to correctness and need some expert assistance 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





view thread (8+ messages)  latest in thread

Message-ID: <1674346.1700665147@sss.pgh.pa.us>
Permalink:  ../1674346.1700665147@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/1674346.1700665147@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-general@postgresql.org
  Cc: tgl@sss.pgh.pa.us, cgg007@yahoo.com, a.mantzios@cloud.gatewaynet.com
  Subject: Re: Removing oids with pg_repack
  In-Reply-To: <1674346.1700665147@sss.pgh.pa.us>
  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> <1674346.1700665147@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