From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Bernd Helmle <mailings(at)oopsware(dot)de>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pg_dump and minor versions |
Date: | 2007-06-29 14:57:43 |
Message-ID: | 12922.1183129063@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Fri, Jun 29, 2007 at 03:09:30PM +0200, Bernd Helmle wrote:
>> While playing around with various postgresql installations i recognized
>> that pg_dump complaints even within major-releases about different
>> minor-numbers, such as:
>>
>> pg_dump: server version: 8.2.4; pg_dump version: 8.2.0
>>
>> I thought we are safe against pg_dump changes within a minor release, or
>> i'm wrong?
> Unless there are fixes *in* pg_dump.
The specific problem is that there might be a server behavioral change
that pg_dump has to compensate for. (Obviously this is not very
desirable, but we've had to make such changes in minor releases in the
past.) 8.2.0 pg_dump cannot know the future, so it has to err on the
side of caution and complain when it sees a newer server version.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2007-06-29 15:02:41 | Re: Configurable Additional Stats |
Previous Message | Simon Riggs | 2007-06-29 14:15:33 | Re: SetBufferCommitInfoNeedsSave and race conditions |