From: Tom Lane <tgl@sss.pgh.pa.us>
To: Andreas Pflug <pgadmin@pse-consulting.de>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Possible TODO item: copy to/from pipe
Date: Wed, 31 May 2006 16:10:32 -0400
Message-ID: <15060.1149106232@sss.pgh.pa.us> (raw)
In-Reply-To: <447DD1D7.20001@pse-consulting.de>
References: <12436.1149087794@sss.pgh.pa.us>
<447DB844.6010507@pse-consulting.de>
<447DB910.2020607@pse-consulting.de>
<13208.1149093007@sss.pgh.pa.us>
<447DCFAF.4070308@commandprompt.com>
<447DD1D7.20001@pse-consulting.de>
Andreas Pflug <pgadmin@pse-consulting.de> writes:
> My COPY WITH COMPRESSION is not the same as taking a copy file and
> zipping it; it creates a copy file with BinarySignature that has
> compressed bytes in the data part, thus it can be handled by any client
> app that can stream binary copy files from/to the server.
If you mean you're compressing each data field separately, that's surely
a very bad idea. If you mean you're compressing everything except the
file header, I fail to see the value. Binary is binary. I *seriously*
doubt there are clients out there that look for a PGCOPY header before
deciding whether to send the file to the server or not. And a client
that did know that much about a PGCOPY file would likely spit up on a
critical flag it didn't recognize, anyway.
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, pgadmin@pse-consulting.de, jd@commandprompt.com
Subject: Re: Possible TODO item: copy to/from pipe
In-Reply-To: <15060.1149106232@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