Putting OIDs etc back into pg_dump? - Mailing list pgsql-hackers

From Richard Huxton
Subject Putting OIDs etc back into pg_dump?
Date
Msg-id 40D96F90.6050204@archonet.com
Whole thread Raw
Responses Re: Putting OIDs etc back into pg_dump?
List 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
butnot 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


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: COPY security fix
Next
From: Ferruccio Zamuner
Date:
Subject: Weird NOT IN condition in SELECT (PostgreSQL 7.4.3 and 7.4.2 tested)