Re: pg_dump and BINARY mode COPY

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

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.

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

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2007-12-06 18:26:34 Going to Japan
Previous Message Tom Lane 2007-12-06 18:18:51 Re: [HACKERS] BUG #3799: csvlog skips some logs