From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Hannu Krosing <hannu(at)tm(dot)ee> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, Rod Taylor <rbt(at)zort(dot)ca>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: db partial dumping with pg_dump |
Date: | 2002-08-13 19:03:21 |
Message-ID: | 200208131903.g7DJ3Lu16950@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Actually, loading all this stuff into COPY is not the way to go, I
think.
Informix had:
UNLOAD TO 'filename'
SELECT ...
I have to admit, this is a superior way to do thing compared to what we
have. Is is possible for us to get:
COPY TO 'filename'
SELECT ...
It allows any arbitrary table, group by, even order by combination.
---------------------------------------------------------------------------
Hannu Krosing wrote:
> On Tue, 2002-08-13 at 20:24, Tom Lane wrote:
> >
> > What would seem to make sense is adding a WHERE-clause option to
> > COPY TO, and then you could go
> > COPY table TO 'myfile' WHERE ...
>
> What about :
>
> COPY table TO 'myfile' [ WHERE cond ] [ AS INSERT [ WITH COLUMN ] ];
>
> to get the data as INSERT INTO statements (pg_dump -d), with optional
> column list (pg_dump -D)
>
> ----------------
> Hannu
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
--
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
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-08-13 19:10:09 | Re: Temporary Views |
Previous Message | strange | 2002-08-13 18:39:01 | Re: [HACKERS] Linux Largefile Support In Postgresql RPMS |