Change in "policy" on dump ordering?

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Change in "policy" on dump ordering?
Date: 2017-02-21 19:58:48
Message-ID: 87866740-ef55-8a6d-6480-499b92aa23c0@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: 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)

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2017-02-21 20:05:19 Re: pg_dump does not refresh matviews from extensions
Previous Message Jim Nasby 2017-02-21 19:54:17 pg_dump does not refresh matviews from extensions