| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Rod Taylor <pg(at)rbt(dot)ca> |
| Cc: | tshipley(at)deru(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: feature proposal ... |
| Date: | 2005-09-22 01:02:38 |
| Message-ID: | 433202AE.8080605@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Rod Taylor wrote:
>You either have code issuing the commands and collecting the results
>making a standard select just as fast or you are using psql which
>already has multiple display types for SELECT data, including XML
>output, but another could easily be added for CSV style output.
>
>
>
We have CSV output now and it's produced by the server. psql's \copy is
in fact just a very thin veneer over the server-side COPY. Besides, we
might well be using another client - your assertion that if COPY output
is going to the client it must be psql is simply wrong.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-09-22 01:10:13 | 2 forks for md5? |
| Previous Message | Rod Taylor | 2005-09-22 00:34:16 | Re: feature proposal ... |