Re: Patch for pg_dump

From: "Dany DeBontridder" <dany118(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Patch for pg_dump
Date: 2007-03-22 09:19:11
Message-ID: c40e6c010703220219l73d20bd9gdc040108cc32f526@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/21/07, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > I guess this matches this TODO item:
> > o Allow selection of individual object(s) of all types, not just
> > tables
> (...)
> Code-wise, the patch seems a bit of a mess too --- it will certainly not
> scale up to dumping some functions and some other things, as one would
> expect for instance if one said "pg_dump -Q myfunc -t mytab ...". It
> doesn't even look like it will handle multiple -Q switches. I think a
> minimum expectation is that -Q would work like -t now does.

Well it was my first patch :-) So I suggest to use a generic argument like
--object=function, which could be extended later to object=type, table,
sequence, trigger... But now I have another problem: how to specify a name ?

regards,

D.

>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Csaba Nagy 2007-03-22 09:22:48 Re: CREATE INDEX and HOT - revised design
Previous Message Hannu Krosing 2007-03-22 09:03:24 Re: Fixing hash index build time