Обсуждение: pg_dump and minor versions

Short question:

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?

--  Thanks
                   Bernd

On Fri, Jun 29, 2007 at 03:09:30PM +0200, Bernd Helmle wrote:
> Short question:
> 
> 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. You should always try to use the
latest minor version for both server and client tools, since they contain
important bugfixes in general. That said, it will mosto ften work fine with
an older minor version one.

//Magnus

--On Freitag, Juni 29, 2007 15:32:19 +0200 Magnus Hagander 
<magnus@hagander.net> wrote:

> On Fri, Jun 29, 2007 at 03:09:30PM +0200, Bernd Helmle wrote:
>> Short question:
>>
>> 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. You should always try to use the
> latest minor version for both server and client tools, since they contain
> important bugfixes in general. That said, it will mosto ften work fine
> with an older minor version one.
>

Okay i understand...i always advice people to use the most recent version, 
but i was a little bit surprised that we force -i even in minor releases if 
we encounter a version mismatch (the other way spoken: i was in the opinion 
we check against major number only). Thanks for the clarification...

--  Thanks
                   Bernd

Magnus Hagander <magnus@hagander.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