Putting OIDs etc back into pg_dump?

From: Richard Huxton <dev(at)archonet(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Putting OIDs etc back into pg_dump?
Date: 2004-06-23 11:54:56
Message-ID: 40D96F90.6050204@archonet.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

There was a recent post on -performance where someone had run
pg_resetxlog and nuked their transaction counter. Whenever someone has
filesystem-level problems like this they need to know:
- "current" transaction ID
- OIDs of system objects

Of course, OIDs have been removed from a standard pg_dump so different
installations can diff their schemas (and a good thing too).

So - should this information be:
1. Logged nightly via standard logging procedures.
2. Stored in a format=custom dump but not for textual schemas.
3. Stored in a different file, that is updated on occasion
4. Not stored at all, it's pointless.
5. Not stored at all, PITR means this is academic now.

--
Richard Huxton
Archonet Ltd

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2004-06-23 12:57:11 Re: nested xacts and phantom Xids
Previous Message Bruce Momjian 2004-06-23 10:14:15 COPY security fix