Re: db partial dumping with pg_dump

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:34:59
Message-ID: 200208131934.g7DJYxT22371@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hannu Krosing wrote:
> On Wed, 2002-08-14 at 00:03, Bruce Momjian wrote:
> >
> > 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.
>
>
> It would be more in line with the rest of the system to just allow
> subselect as 'table'
>
> COPY (select in,name from mystuff wher id > 10) over10stuff TO stdout;

Yep, that would work too. Clearly, we should shoot for something that
leverages the existing SELECT code rather than hang more clauses off of
COPY.

--
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

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-13 19:38:13 Re: Everything is now "required by the database system"
Previous Message Tom Lane 2002-08-13 19:30:48 Re: Temporary Views