From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] COPY .. COMPRESSED |
Date: | 2013-01-14 16:28:30 |
Message-ID: | 20130114162830.GL16126@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > I do like the idea of a generalized answer which just runs a
> > user-provided command on the server but that's always going to require
> > superuser privileges.
>
> The design that was being kicked around allowed pipes to be used on the
> client side too, ie \copy foo to '| gzip ...'. That form would not
> require any special privileges, and might be thought preferable for
> another reason too: it offloads the work from the server.
It's a different use-case which, imv, is really already trivially
covered:
psql -c 'COPY foo TO STDOUT;' | gzip > myfile.gz
While there is no option currently for having the server do the
compression before sending the data over the wire.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2013-01-14 16:32:49 | Re: json api WIP patch |
Previous Message | Amit kapila | 2013-01-14 16:27:33 | Re: Proposal for Allow postgresql.conf values to be changed via SQL [review] |