From: Tom Lane <tgl@sss.pgh.pa.us>
To: pgsql-hackers@postgreSQL.org
Subject: Possible TODO item: copy to/from pipe
Date: Wed, 31 May 2006 11:03:14 -0400
Message-ID: <12436.1149087794@sss.pgh.pa.us> (raw)
After re-reading what I just wrote to Andreas about how compression of
COPY data would be better done outside the backend than inside, it
struck me that we are missing a feature that's fairly common in Unix
programs. Perhaps COPY ought to have the ability to pipe its output
to a shell command, or read input from a shell command. Maybe something
like
COPY mytable TO '| gzip >/home/tgl/mytable.dump.gz';
(I'm not wedded to the above syntax, it's just an off-the-cuff thought.)
Of course psql would need the same capability, since the server-side
copy would still be restricted to superusers.
You can accomplish COPY piping now through psql, but it's a bit awkward:
psql -c "COPY mytable TO stdout" mydb | gzip ...
Thoughts? Is this worth doing, or is the psql -c approach good enough?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tgl@sss.pgh.pa.us
Subject: Re: Possible TODO item: copy to/from pipe
In-Reply-To: <12436.1149087794@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox