Re: Updating OID column

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: pgsql-hackers(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Martijn van Oosterhout <kleptog(at)svana(dot)org>, Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
Subject: Re: Updating OID column
Date: 2006-04-10 16:18:16
Message-ID: 200604101818.17153.peter_e@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> Right. I looked at this awhile back, though, and found multiple
> places that would break if you tried it :-( --- mainly assumptions
> about the meaning of resno in target lists. (The comments for the
> TargetEntry struct give some but not all of the details.) Given that
> OID is semi-deprecated anyway these days, it's not clear it's worth
> fixing.

I came across this while restoring a botched backup. I imported a
schema dump and copied over various data files, adjusted the
transaction IDs, relfilenodes, etc., but the OIDs of the TOAST tables
are stored in the fields, so it seemed that the OIDs of the TOAST table
entries in pg_class would have to be adjusted. I managed to fix up the
few broken references manually in a binary editor, but having OIDs
updatable would have been handy if more TOAST values had needed fixing.

--
Peter Eisentraut
http://developer.postgresql.org/~petere/

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2006-04-10 17:36:45 Re: Support Parallel Query Execution in Executor
Previous Message Tom Lane 2006-04-10 15:29:29 Re: Updating OID column