Re: pg_dump, libdump, dump API, & backend again - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg_dump, libdump, dump API, & backend again
Date
Msg-id Pine.LNX.4.21.0007251912460.546-100000@localhost.localdomain
Whole thread Raw
In response to Re: pg_dump, libdump, dump API, & backend again  (Philip Warner <pjw@rhyme.com.au>)
List pgsql-hackers
Philip Warner writes:

> >* order
> 
> This is an issue for the client. I am not proposing a
> 'Dump_The_Entire_Datbase' call; just a
> 'Dump_One_Thing_And_A_List_Of_Dependencies' call.

How? Functions can only return one value reliably.

> >* How to resolve circular dependencies?
> 
> Issue for the client.

Not really. If you have a circular dependency `table --(column default)-->
function --(reads)--> table' then you need to dump the table differently
(perhaps leave out the constraint and add it after the function is
created).


-- 
Peter Eisentraut                  Sernanders väg 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: Re: Problem with disabling triggers in pg_dump
Next
From: Peter Eisentraut
Date:
Subject: Re: INET/CIDR types