Re: db partial dumping with pg_dump

From: Hannu Krosing <hannu(at)tm(dot)ee>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
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 17:34:45
Message-ID: 1029260085.4742.55.camel@rh72.home.ee
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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;

-----------------
Hannu

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2002-08-13 17:38:37 Re: Everything is now "required by the database system"
Previous Message Hannu Krosing 2002-08-13 17:31:27 Re: Temporary Views