Re: 9.3beta2: Failure to pg_upgrade - Mailing list pgsql-bugs

$ 9.2_dev/bin/pg_controldata data
pg_control version number:            922
Catalog version number:               201204301
Database system identifier:           5789770930315980286
Database cluster state:               shut down
pg_control last modified:             Tue 30 Jul 2013 09:57:54 AM EDT
Latest checkpoint location:           6C/F8EE7500
Prior checkpoint location:            6C/F8E90C18
Latest checkpoint's REDO location:    6C/F8EE7500
Latest checkpoint's TimeLineID:       1
Latest checkpoint's full_page_writes: on
Latest checkpoint's NextXID:          0/15960984
Latest checkpoint's NextOID:          4747737
Latest checkpoint's NextMultiXactId:  2982
Latest checkpoint's NextMultiOffset:  6479
Latest checkpoint's oldestXID:        1761
Latest checkpoint's oldestXID's DB:   12843
Latest checkpoint's oldestActiveXID:  0
Time of latest checkpoint:            Tue 30 Jul 2013 09:57:53 AM EDT
Minimum recovery ending location:     0/0
Backup start location:                0/0
Backup end location:                  0/0
End-of-backup record required:        no
Current wal_level setting:            minimal
Current max_connections setting:      100
Current max_prepared_xacts setting:   0
Current max_locks_per_xact setting:   256
Maximum data alignment:               8
Database block size:                  8192
Blocks per segment of large relation: 131072
WAL block size:                       8192
Bytes per WAL segment:                16777216
Maximum length of identifiers:        64
Maximum columns in an index:          32
Maximum size of a TOAST chunk:        1996
Date/time type storage:               64-bit integers
Float4 argument passing:              by value
Float8 argument passing:              by value


--
Jesse Denardo


On Wed, Jul 31, 2013 at 5:06 PM, Bruce Momjian <bruce@momjian.us> wrote:

> On Wed, Jul 31, 2013 at 12:56:33PM -0400, Alvaro Herrera wrote:
> > Bruce Momjian escribi=C3=B3:
> > > On Tue, Jul 30, 2013 at 10:17:52AM -0400, Jesse Denardo wrote:
> >
> > > So, first, this is new in 9.3, and second, it seems the comment "we
> need
> > > to reset pg_control so that the new server doesn't attempt to read
> > > multis older than the cutoff value" is not working.  Alvaro, can you
> > > comment on this?  I think you added this code with this commit:
> >
> > So it seems.  I will have a look.
>
> Well, the good news is that this is new 9.3 code, this bug was caught
> during beta, and pg_upgrade failed visibly, rather than silently.
>
> --
>   Bruce Momjian  <bruce@momjian.us>        http://momjian.us
>   EnterpriseDB                             http://enterprisedb.com
>
>   + It's impossible for everything to be true. +
>