Postgres Pro
Downloads
Home   >   mailing lists

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

From Peter Eisentraut
Subject Re: [HACKERS] Change in "policy" on dump ordering?
Date
Msg-id 8f64786e-824d-7c0d-33a6-3d9e1c8e9fde@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] Change in "policy" on dump ordering?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Responses Re: [HACKERS] Change in "policy" on dump ordering?  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
Tree view 
On 2/21/17 14:58, Jim Nasby wrote:
> 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 there any specific assignment that you have concerns about?

> Is this change a good or bad idea? Should there be an official guide for 
> where new things go?

The comment above dbObjectTypePriority explains it, doesn't it?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] mat views stats
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] Proposal : For Auto-Prewarm.