From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Naomi Walker <nwalker(at)eldocomp(dot)com> |
Cc: | Bhuvan A <bhuvansql(at)myrealbox(dot)com>, pgsql-admin(at)postgresql(dot)org |
Subject: | Re: loading and unloading rows |
Date: | 2002-11-08 04:46:23 |
Message-ID: | 200211080446.gA84kOw29553@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Naomi Walker wrote:
> Can we add unload/load functionality to the list, please?
>
>
>
> > > >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;
I have thought of that. We would probably join COPY to INSERT/SELECT
rather than use LOAD/UNLOAD. The problem is that the COPY code reads
right out of the table, rather than reading from the executor. This
change would require that. You can do it now by using TEMP tables to do
the 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
From | Date | Subject | |
---|---|---|---|
Next Message | Timothy D McKernan | 2002-11-08 04:47:11 | Uninitialized pages notices |
Previous Message | Timothy D McKernan | 2002-11-08 02:41:09 | Re: Vacuum return codes (vacuum as db integrity check?) |