| From: | Davy Durham <pubaddr5(at)davyandbeth(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: Feature: give pg_dump a WHERE clause expression |
| Date: | 2008-06-02 00:55:57 |
| Message-ID: | 1212368157.17810.90.camel@ubuntu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
On Sun, 2008-06-01 at 20:53 -0400, Stephen Frost wrote:
> * Davy Durham (pubaddr5(at)davyandbeth(dot)com) wrote:
> > The code is not all that much to maintain as it is, and making it an
> > addition to an existing parameter instead of a new one may not increase
> > the code size by much more at all.
>
> I'm generally in favor of 'creature-comfort' kind of additions, but I
> have to agree with Tom on this one. I don't see much of a use case, and
> it's trivial to create a shell-script to do what you're looking for with
> psql and COPY statements.
>
To reiterate, it is not possible to use the COPY command to create
standard SQL INSERT statements that can be conveniently loaded by
another db. No?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2008-06-02 02:02:24 | Re: Feature: give pg_dump a WHERE clause expression |
| Previous Message | Stephen Frost | 2008-06-02 00:53:22 | Re: Feature: give pg_dump a WHERE clause expression |