Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions) - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)
Date
Msg-id 20160212225411.GB4753@momjian.us
Whole thread Raw
In response to Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: NextXID format change (was Re: exposing pg_controldata and pg_config as functions)
List pgsql-hackers
On Thu, Feb 11, 2016 at 07:18:46PM -0500, Bruce Momjian wrote:
> No, that is not an improvement --- see my previous comment:
> 
> > We could get more sophisticated by checking the catalog version number
> > where the format was changed, but that doesn't seem worth it, and is
> > overly complex because we get the catalog version number from
> > pg_controldata, so you would be adding a dependency in ordering of the
> > pg_controldata entries.
> 
> By testing for '906', you prevent users from using pg_upgrade to go from
> one catalog version of 9.6 to a later one.  Few people may want to do
> it, but it should work.

C comment added explaining why we do this.

--  Bruce Momjian  <bruce@momjian.us>        http://momjian.us EnterpriseDB
http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Roman grave inscription                             +



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.
Next
From: Andres Freund
Date:
Subject: Re: Re: [COMMITTERS] pgsql: Add some isolation tests for deadlock detection and resolution.