| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Mark Woodward <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: COPY (query) TO file |
| Date: | 2006-06-03 00:48:03 |
| Message-ID: | 4480DC43.3040209@commandprompt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> Allow COPY to output from views
>> Another idea would be to allow actual SELECT statements in a COPY.
>>
>> Personally I strongly favor the second option as being more flexible
>> than the first.
>
>
> I second that - allowing arbitrary SELECT statements as a COPY source
> seems much more powerful and flexible than just supporting COPY FROM VIEW.
Not to be a sour apple or anything but I don't see how any of this is
needed in the backend since we can easily use Psql to do it, or pretty
much any other tool.
Joshua D. Drake
>
>
> Stefan
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Woodward | 2006-06-03 01:25:41 | Re: COPY (query) TO file |
| Previous Message | Tom Lane | 2006-06-02 23:38:57 | Re: More thoughts about planner's cost estimates |