Re: BUG #11264: Auto vacuum wraparound job blocking everything

Here is the pg_controldata output from 9.1. Thanks. Dinesh

$ /usr/pgsql-9.1/bin/pg_controldata data
pg_control version number:            903
Catalog version number:               201105231
Database system identifier:           5720710153987476471
Database cluster state:               in production
pg_control last modified:             Sat 19 Jul 2014 07:05:08 AM GMT
Latest checkpoint location:           FC0/25643788
Prior checkpoint location:            FC0/169F2238
Latest checkpoint's REDO location:    FC0/1D919830
Latest checkpoint's TimeLineID:       1
Latest checkpoint's NextXID:          0/950483638
Latest checkpoint's NextOID:          1146307754
Latest checkpoint's NextMultiXactId:  20783
Latest checkpoint's NextMultiOffset:  42669
Latest checkpoint's oldestXID:        750608965
Latest checkpoint's oldestXID's DB:   16411
Latest checkpoint's oldestActiveXID:  0
Time of latest checkpoint:            Sat 19 Jul 2014 07:02:38 AM GMT
Minimum recovery ending location:     0/0
Backup start location:                0/0
Current wal_level setting:            minimal
Current max_connections setting:      1024
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

-----Original Message-----
From: Alvaro Herrera [mailto:alvherre@2ndquadrant.com]=20
Sent: Wednesday, August 27, 2014 8:48 AM
To: Dinesh Bhandary
Cc: pgsql-bugs@postgresql.org
Subject: Re: [BUGS] BUG #11264: Auto vacuum wraparound job blocking everyth=
ing

Dinesh Bhandary wrote:

> We used psotgres 9.3.4 to pg_upgrade from 9.1. We just upgraded=20
> binaries to 9.3.5 just last week ? Would this cause any issues with=20
> MultiXid issue.

So you ran 200 million write transactions in one week?

Do you still have the 9.1 data from before the upgrade?  If so, would you p=
aste pg_controldata output from that?

--=20
=C1lvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services