Re: raw output from copy - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: raw output from copy
Date
Msg-id CAFj8pRDoW-LFYYQC05qjUJ8utmong-sZjTXP4a+vrEU21+_xTw@mail.gmail.com
Whole thread Raw
In response to Re: raw output from copy  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers


2015-07-02 15:43 GMT+02:00 Simon Riggs <simon@2ndquadrant.com>:
On 2 July 2015 at 14:02, Andrew Dunstan <andrew@dunslane.net> wrote:

Please don't top-post on the PostgreSQL lists. You've been around here long enough to know that bottom posting is our custom.

I posted a patch for this in 2013 at <http://www.postgresql.org/message-id/50F2FA92.9040000@dunslane.net> but it can apply to a SELECT, and doesn't need COPY. Nobody seemed very interested, so I dropped it. Apparently people now want something along these lines, which is good.

It's a shame that both solutions are restricted to either COPY or psql. 

Both of those are working on suggestions from Tom, so there is no history of preference there.

Can we have both please, gentlemen?

If we implemented Andrew's solution, how would we request it in a COPY statement? Seems like we would want the RAW format keyword anyway.

I prefer a COPY like solution - it can be used on both sides (server, client), and it can be used little bit simply for psql -c "XXX" pattern.

Regards

Pavel



--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: drop/truncate table sucks for large values of shared buffers
Next
From: Andrew Dunstan
Date:
Subject: Re: raw output from copy