I use often pgdump... and we have many bytea on our database...
Without binary COPY, backup is very slow and takes 4x more space on the
network wire...
It would be great to have an option (--binary) with eventually a WARNING
message (that your backup could be not portable across architecture...)
b
On Thu, 2007-12-06 at 13:22 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
> >> To preserve platform and version independence of the dump.
>
> > Only if there is a risk. Since a common route to upgrade is a
> > dump/restore b
Simon Riggs <[EMAIL PROTECTED]> writes:
> On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
>> To preserve platform and version independence of the dump.
> Only if there is a risk. Since a common route to upgrade is a
> dump/restore back onto same box it seems worth having an option to do
> this.
On Thu, 2007-12-06 at 12:43 -0500, Tom Lane wrote:
> Simon Riggs <[EMAIL PROTECTED]> writes:
> > Is there a reason why pg_dump avoids using BINARY mode COPY?
>
> To preserve platform and version independence of the dump.
OK, thats what I guessed.
> > Unless there is a specific reason not to we c
Simon Riggs <[EMAIL PROTECTED]> writes:
> Is there a reason why pg_dump avoids using BINARY mode COPY?
To preserve platform and version independence of the dump.
> Unless there is a specific reason not to we could/should allow an option
> on the dump.
Is there any evidence to show that there'd b
On Thu, Dec 06, 2007 at 05:30:02PM +, Simon Riggs wrote:
> Is there a reason why pg_dump avoids using BINARY mode COPY?
> (Or am I missing something?)
>
> Unless there is a specific reason not to we could/should allow an option
> on the dump.
Probably because BINARY dumps arn't portable. Just
