Re: loading and unloading rows - Mailing list pgsql-admin

From Naomi Walker
Subject Re: loading and unloading rows
Date
Msg-id 5.1.0.14.2.20021102133720.00a24250@imap.eldocomp.com
Whole thread Raw
In response to Re: loading and unloading rows  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: loading and unloading rows
List pgsql-admin
Exactly.  My Informix background is showing.  Is there a way to officially
get this put on a to do list?  I'd be most appreciative of the value this adds.

Slightly off subject, is there a way to read from one cluster and insert
into a database in another cluster (local or remote)?  I think I read this
is coming in the future.  In Informix-land, we used to do this through a
named pipe.  It was quite handy.

At 10:39 PM 11/1/02 -0500, Bruce Momjian wrote:

>Yes, agreed, it would be nice to have WHERE as part of COPY.  In fact, I
>like Informix's solution, which merges data in/out with INSERT/SELECT:
>
>         UNLOAD TO '/tmp/x'
>         SELECT *
>         FROM tab;
>
>and
>
>         LOAD FROM '/tmp/x'
>         INSERT INTO tab;
>
>It is tough to beat this flexibility.
>
>---------------------------------------------------------------------------
>
>Naomi Walker wrote:
> >
>
> > The problem with COPY, I think, is that I cannot use a WHERE
> > statement.  I'd like to just unload certain rows from a table.  If I
> wanted
> > the whole table, i'll do a pg_dump or copy.
> >
>
> > Again, i'd like a way to easily unload some selected rows  (select * table
> > where foo=X) from a table, and save them, or load them in another cluster,
> > etc.  Short of writing them to a temp table, then pg_dumping, or some
> > klunk-oid mething, I do not see a clean way.
> >
> > Back to the maddening crowd.  Anyone at least agreed this is
> needed?  Could
> > we add "where"  clauses to COPY?  That would be perfect.
> >


pgsql-admin by date:

Previous
From: "Marc Mitchell"
Date:
Subject: Re: DB Performance
Next
From: "working4aliving"
Date:
Subject: Re: pg_hba.conf on win32