[HACKERS] Change in "policy" on dump ordering? - Mailing list pgsql-hackers

From Jim Nasby
Subject [HACKERS] Change in "policy" on dump ordering?
Date
Msg-id 87866740-ef55-8a6d-6480-499b92aa23c0@BlueTreble.com
Whole thread Raw
Responses Re: [HACKERS] Change in "policy" on dump ordering?  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
AFAICT in older versions only object types that absolutely had to wait 
for DO_POST_DATA_BOUNDARY would do so. More recently though, objects are 
being added after that (presumably because it's easier than renumbering 
everything in dbObjectTypePriority).

Is this change a good or bad idea? Should there be an official guide for 
where new things go?
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Jim Nasby
Date:
Subject: [HACKERS] pg_dump does not refresh matviews from extensions
Next
From: Stephen Frost
Date:
Subject: Re: [HACKERS] pg_dump does not refresh matviews from extensions