Re: pg_dump option to dump only functions - Mailing list pgsql-hackers

From Tino Wildenhain
Subject Re: pg_dump option to dump only functions
Date
Msg-id 1128850486.18052.60.camel@Andrea.peacock.de
Whole thread Raw
In response to Re: pg_dump option to dump only functions  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump option to dump only functions
List pgsql-hackers
Am Samstag, den 08.10.2005, 18:03 -0400 schrieb Tom Lane:
> Josh Berkus <josh@agliodbs.com> writes:
> >> I was wonderring, because I create a lot of server side utility functions,
> >> whether adding an option to pg_dump to just dump functions has been
> >> considered. I did a quick perusal of the code, and noted that there is a
> >> separate section within pg_dump to get the functions, but it is not able to
> >> be triggered separately from schema and data. Any reason why this wouldn't
> >> be a good(tm) idea?
> 
> > It would be an *excellent* idea, along with options to dump specific 
> > functions, and both specific and all views/types/operators.  Go for it.
> 
> I kinda thought we had a TODO entry for that already, but I see we
> don't.
> 
> Another thing you'd find yourself wanting very quickly is an option to
> follow dependencies, ie "dump these objects plus everything they depend
> on".  Otherwise you'd have to find the dependencies manually, which
> would get real tedious in any complex schema.
> 
> Proposed TODO entries for pg_dump:
> 
> * Allow selection of individual object(s) of all types, not just tables
> * In a selective dump, allow dumping of all dependencies of the objects

May I suggest the implementation of -l / -L like pg_restore has?
So you can work the same way to produce the list of objects
to dump and manipulate them - as well as adding the depencies
tracking option to pg_restore?

Regards
Tino



pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Issue is changing _bt_compare function and
Next
From: Volkan YAZICI
Date:
Subject: How TODO prevent PQfnumber() from lowercasing?