Re: pg_dump option to dump only functions

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tino Wildenhain <tino(at)wildenhain(dot)de>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org, Sean Utt <sean(at)strateja(dot)com>
Subject: Re: pg_dump option to dump only functions
Date: 2005-10-12 02:57:41
Message-ID: 200510120257.j9C2vf016273@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tino Wildenhain wrote:
> > 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?

Good idea, added:

o Add options like pg_restore -l and -L to pg_dump

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-10-12 03:25:08 Re: How TODO prevent PQfnumber() from lowercasing?
Previous Message Tom Lane 2005-10-12 02:42:49 Re: database vacuum from cron hanging