On Jun 18, 10:44 pm, alvhe...@xxxxxxxxxxxxxxxxx (Alvaro Herrera) wrote: > > Please check "MultiXact" id consumption. Do you mean that your server > has crashed? > How do I check MilitXact id consumption ? Is it "Latest checkpoint's NextXID:" in the output of pg_controldata ? transaction id consumption is ~ 350000 per day (extrapolated from 16 hours). No, the Server has been up for about 2 month (regular reboot due to kernel and postgresql upgrade to 8.1.8), was running before for 7 month flawless, and before that i migrated from 8.0 to 8.1.4 with a complete dump/restore). pg_multixact/members shows: -rw------- 1 postgres postgres 8192 Aug 30 2006 0000 pg_multixact/offsets shows: -rw------- 1 postgres postgres 8192 Apr 13 15:03 0000 pg_controldata shows: pg_control version number: 812 Catalog version number: 200510211 Database system identifier: 4969068620492422615 Database cluster state: in production pg_control last modified: Tue Jun 19 08:00:36 2007 Current log file ID: 10 Next log file segment: 102 Latest checkpoint location: A/65362150 Prior checkpoint location: A/652E091C Latest checkpoint's REDO location: A/65362150 Latest checkpoint's UNDO location: 0/0 Latest checkpoint's TimeLineID: 1 Latest checkpoint's NextXID: 99983151 Latest checkpoint's NextOID: 7758309 Latest checkpoint's NextMultiXactId: 1 Latest checkpoint's NextMultiOffset: 0 Time of latest checkpoint: Tue Jun 19 08:00:36 2007 Maximum data alignment: 4 Database block size: 8192 Blocks per segment of large relation: 131072 Bytes per WAL segment: 16777216 Maximum length of identifiers: 64 Maximum columns in an index: 32 Date/time type storage: floating-point numbers Maximum length of locale name: 128 LC_COLLATE: C LC_CTYPE: C regards Gerhard
