Re: pg_dump and BINARY mode COPY - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: pg_dump and BINARY mode COPY
Date
Msg-id 1196965938.4255.433.camel@ebony.site
Whole thread Raw
In response to Re: pg_dump and BINARY mode COPY  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_dump and BINARY mode COPY  (Hubert FONGARNAND <informatique.internet@fiducial.fr>)
List pgsql-hackers
On Thu, 2007-12-06 at 13:22 -0500, Tom Lane wrote:
> Simon Riggs <simon@2ndquadrant.com> 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.
> 
> I think you missed the point about version independence.  That would be
> exactly the scenario where a version-to-version change in binary format
> --- for instance, "money" widening to 64 bits in 8.3 --- would burn you.

OK

> Furthermore, this doesn't seem like a scenario where performance ought
> to be the primary concern.  How often do you do major version upgrades?

Not often enough.

If it was faster, we would rely on more people actually doing it.

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Going to Japan
Next
From: Guillaume Lelarge
Date:
Subject: Re: shared_buffers, wal_buffers, WAL files, data files