Putting OIDs etc back into pg_dump?

Поиск
Список
Период
Сортировка
От Richard Huxton
Тема Putting OIDs etc back into pg_dump?
Дата
Msg-id 40D96F90.6050204@archonet.com
обсуждение исходный текст
Ответы Re: Putting OIDs etc back into pg_dump?  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
Список 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 по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: COPY security fix
Следующее
От: Ferruccio Zamuner
Дата:
Сообщение: Weird NOT IN condition in SELECT (PostgreSQL 7.4.3 and 7.4.2 tested)