From: | Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
---|---|
To: | Rod Taylor <pg(at)rbt(dot)ca> |
Cc: | eg(at)cybertec(dot)at, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: feature proposal ... |
Date: | 2005-09-21 14:01:30 |
Message-ID: | 433167BA.9040705@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Rod Taylor wrote:
>>the problem is: COPY can write data returned by a SELECT statement to a
>>file. our idea is to implement precisely that.
>>
>>example:
>>
>>COPY TO file_name USING some_select_statement;
>
>
> I have run into plenty of cases where I wanted to dump part of a
> structure and this could be used for that, but I've always found that
> temporary tables were sufficient and equally SQL scriptable
>
> CREATE TEMP TABLE tab AS SELECT ...; COPY tab TO file_name;
Hi Rod,
TEMP TABLE are not suitable for my case. Using a temp table would
essentially mean that we had to store the data 3 times: Original data,
temp table + dump. Temp tables are only fine for small amounts of data
but we are talking about too much data here (my smallest export will
contain 15.000.000 records).
Best regards,
Hans
--
Cybertec Geschwinde & Schönig GmbH
Schöngrabern 134; A-2020 Hollabrunn
Tel: +43/1/205 10 35 / 340
www.postgresql.at, www.cybertec.at
From | Date | Subject | |
---|---|---|---|
Next Message | Paolo Magnoli | 2005-09-21 14:03:17 | R: feature proposal ... |
Previous Message | Rod Taylor | 2005-09-21 13:46:00 | Re: feature proposal ... |