Re: pg_dump and BINARY mode COPY

From: Simon Riggs <simon(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: pg_dump and BINARY mode COPY
Date: 2007-12-06 18:32:18
Message-ID: 1196965938.4255.433.camel@ebony.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, 2007-12-06 at 13:22 -0500, Tom Lane wrote:
> Simon Riggs <simon(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Guillaume Lelarge 2007-12-06 18:43:59 Re: shared_buffers, wal_buffers, WAL files, data files
Previous Message Decibel! 2007-12-06 18:28:13 Re: [PATCHES] Better default_statistics_target