Re: "column i.indnkeyatts does not exist" in pg_upgrade from 11dev to 11b1 - Mailing list pgsql-hackers

From Tom Lane
Subject Re: "column i.indnkeyatts does not exist" in pg_upgrade from 11dev to 11b1
Date
Msg-id 735.1527626316@sss.pgh.pa.us
Whole thread Raw
In response to Re: "column i.indnkeyatts does not exist" in pg_upgrade from 11devto 11b1  (Justin Pryzby <pryzby@telsasoft.com>)
List pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes:
> On Tue, May 29, 2018 at 02:00:20PM -0400, Tom Lane wrote:
>> Yeah, that :-(.  pg_dump's approach to cross-version catalog differences
>> can only cope with differences between major versions.  So if it sees
>> a server that calls itself 11-something it's going to think that means
>> the current catalog layout.  There's no good way to deal with pre-beta
>> snapshot versions, other than to dump with a pg_dump of the same vintage.

> Thanks for confirming.

> In this case I worked around it by doing:
>  sudo ln -sfv /usr/pgsql-11{dev0,b1}/bin/pg_dump
>  sudo ln -sfv /usr/pgsql-11{dev0,b1}/bin/pg_dumpall

> I guess, if need be, pg_dump could look at CATALOG_VERSION..

Yeah, if somebody cared to take on a bunch more maintenance effort,
it'd be possible to distinguish at that level of detail.  So far
it hasn't seemed worth the trouble.

            regards, tom lane


pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: Few comments on commit 857f9c36 (skip full index scans )
Next
From: Michael Paquier
Date:
Subject: Supporting tls-server-end-point as SCRAM channel binding for OpenSSL1.0.0 and 1.0.1