Re: [HACKERS] Ordering of pg_dump output - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject Re: [HACKERS] Ordering of pg_dump output
Date
Msg-id m12IGFJ-0003kMC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
In response to Ordering of pg_dump output  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> The simplest real solution I've heard so far is to dump database objects
> in order by OID rather than doing it strictly by type.
>
> Is anyone working on this, or does anyone want to?  I haven't looked at
> pg_dump in a while, but I know some other folks have been hacking it
> recently.
   Dumping  by  Oid  or building up a framework of dependencies,   these where the options. Don't forget, SQL language
functions  are  (in  contrast to procedural ones) parsed at CREATE time.   So any operator, aggregate  or  table  you
use inside  must   exist.  And  they  can  be used in turn in many places, so it   isn't simple at all.
 
   I think finally pg_dump  must  scan  the  entire  schema  two   times,  first  to  get  all the Oid's, second to
dumpall the   objects.
 
   AFAIK, nobody is working on it. And starting on it right  now   seems a little late to make it until BETA.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #




pgsql-hackers by date:

Previous
From: Don Baccus
Date:
Subject: Re: [HACKERS] Ordering of pg_dump output
Next
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Deferred trigger queue