From: Bruce Momjian <bruce@momjian.us>
To: rammohan ganapavarapu <rammohanganap@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Postgresql Upgrade from 9.3 to 9.4 failing
Date: Mon, 30 Oct 2017 22:32:25 -0400
Message-ID: <20171031023225.GA14238@momjian.us> (raw)
In-Reply-To: <CALm_VjjCYcZG7UnDYU6VvgC9dOADaQKieGEmMXDeWuoyd6kUog@mail.gmail.com>
References: <CALm_VjjCYcZG7UnDYU6VvgC9dOADaQKieGEmMXDeWuoyd6kUog@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
fOn Mon, Oct 30, 2017 at 11:16:19AM -0700, rammohan ganapavarapu wrote:
>
> Hi,
>
> I am getting this error when i try to upgrade from psotgresql 9.3 to 9.4 any
> idea ?
It looks like it didn't find anything matching. Could it be confused by
a non-English locale? We have code that should prevent that, but maybe
it isn't working. What OS is this? What is the locale?
---------------------------------------------------------------------------
> "The old cluster lacks some required control information:", " checkpoint next
> XID", " latest checkpoint next OID", " latest checkpoint next MultiXactId", "
> latest checkpoint next MultiXactOffset", " first WAL segment after reset", "
> maximum alignment", " block size", " large relation segment size", " WAL block
> size", " WAL segment size", " maximum identifier length", " maximum number of
> indexed columns", " maximum TOAST chunk size", " dates/times are integers?", "
> float8 argument passing method", " data checksum version", "", "Cannot continue
> without required control information, terminating", "Failure, exiting", "ERROR:
> PostgreSQL Upgrade FAILED"
>
>
> 9.3 control data:
>
> pg_control version number: 937
> Catalog version number: 201306121
> Database system identifier: 6376954828819496929
> Database cluster state: shut down
> pg_control last modified: Sun 29 Oct 2017 12:07:59 PM UTC
> Latest checkpoint location: 8/2B62C18
> Prior checkpoint location: 8/2AE97D0
> Latest checkpoint's REDO location: 8/2B62C18
> Latest checkpoint's REDO WAL file: 000000010000000800000002
> Latest checkpoint's TimeLineID: 1
> Latest checkpoint's PrevTimeLineID: 1
> Latest checkpoint's full_page_writes: on
> Latest checkpoint's NextXID: 0/1557113
> Latest checkpoint's NextOID: 84904 #
> Latest checkpoint's NextMultiXactId: 1
> Latest checkpoint's NextMultiOffset: 0
> Latest checkpoint's oldestXID: 1309
> Latest checkpoint's oldestXID's DB: 1
> Latest checkpoint's oldestActiveXID: 0
> Latest checkpoint's oldestMultiXid: 1
> Latest checkpoint's oldestMulti's DB: 1
> Fake LSN counter for unlogged rels: 0/1
> Minimum recovery ending location: 0/0
> Min recovery ending loc's timeline: 0
> Backup start location: 0/0
> Backup end location: 0/0
> End-of-backup record required: no
> Current wal_level setting: hot_standby
> Current max_connections setting: 100
> Current max_prepared_xacts setting: 0
> Current max_locks_per_xact setting: 64
> 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
> Data page checksum version: 0
>
>
> 9.4 control data;
>
> pg_control version number: 942
> Catalog version number: 201409291
> Database system identifier: 6482307767365018368
> Database cluster state: shut down
> pg_control last modified: Sun 29 Oct 2017 02:20:20 PM UTC
> Latest checkpoint location: 0/16F3D60
> Prior checkpoint location: 0/16F3CF8
> Latest checkpoint's REDO location: 0/16F3D60
> Latest checkpoint's REDO WAL file: 000000010000000000000001
> Latest checkpoint's TimeLineID: 1
> Latest checkpoint's PrevTimeLineID: 1
> Latest checkpoint's full_page_writes: on
> Latest checkpoint's NextXID: 0/1317
> Latest checkpoint's NextOID: 12753
> Latest checkpoint's NextMultiXactId: 1
> Latest checkpoint's NextMultiOffset: 0
> Latest checkpoint's oldestXID: 1308
> Latest checkpoint's oldestXID's DB: 1
> Latest checkpoint's oldestActiveXID: 0
> Latest checkpoint's oldestMultiXid: 1
> Latest checkpoint's oldestMulti's DB: 1
> Time of latest checkpoint: Sun 29 Oct 2017 02:20:20 PM UTC
> Fake LSN counter for unlogged rels: 0/1
> Minimum recovery ending location: 0/0
> Min recovery ending loc's timeline: 0
> Backup start location: 0/0
> Backup end location: 0/0
> End-of-backup record required: no
> Current wal_level setting: hot_standby
> Current max_connections setting: 0
> Current max_prepared_xacts setting: 200
> Current max_locks_per_xact setting: 8
> Maximum data alignment:
> Database block size: 0
> Blocks per segment of large relation: 1093850759
> WAL block size: 8192
> Bytes per WAL segment: 131072
> Maximum length of identifiers: 8192
> Maximum columns in an index: 16777216
> Maximum size of a TOAST chunk: 64
> Date/time type storage: 64-bit integers
> Float4 argument passing: by reference
> Float8 argument passing: by reference
> Data page checksum version: 1996
>
>
> Thanks,
> Ram
--
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. +
+ Ancient Roman grave inscription +
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: bruce@momjian.us, rammohanganap@gmail.com
Subject: Re: Postgresql Upgrade from 9.3 to 9.4 failing
In-Reply-To: <20171031023225.GA14238@momjian.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox