Skip site navigation (1) Skip section navigation (2)

Re: COPY (query) TO file

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 (view raw or flat)
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/



In response to

Responses

pgsql-hackers by date

Next:From: Mark WoodwardDate: 2006-06-03 01:25:41
Subject: Re: COPY (query) TO file
Previous:From: Tom LaneDate: 2006-06-02 23:38:57
Subject: Re: More thoughts about planner's cost estimates

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group