Re: apparent wraparound

> "George Pavlov" <gpavlov(at)mynewplace(dot)com> writes:
> >> During crash recovery?
> > no crashes, just normal DB operation...
>
> Hmm ... what is in pg_multixact/members/ again?

Now there is only a file named 0010 the date on which changes about
every 4-5 minutes or so. I only noticed the log even with a day+ delay
so no idea what was there at the time of the log event. The DB has not
been restarted since that log event though. Basically nothing abnormal
in the DB operation that I know of around the "apparent wraparound" log
entry and nothing since then...

-rw------- 1 postgres postgres 32768 Nov 10 16:48 0010

> And what do you get from pg_controldata?

Again this is as of right now, not when the log event happened:

pg_control version number: 812
Catalog version number: 200510211
Database system identifier: 4904666118449586173
Database cluster state: in production
pg_control last modified: Fri 10 Nov 2006 04:48:34 PM PST
Current log file ID: 127
Next log file segment: 58
Latest checkpoint location: 7F/39B8A6F8
Prior checkpoint location: 7F/39142790
Latest checkpoint's REDO location: 7F/39B8A6F8
Latest checkpoint's UNDO location: 0/0
Latest checkpoint's TimeLineID: 1
Latest checkpoint's NextXID: 168755857
Latest checkpoint's NextOID: 25532444
Latest checkpoint's NextMultiXactId: 422733
Latest checkpoint's NextMultiOffset: 1056452
Time of latest checkpoint: Fri 10 Nov 2006 04:48:34 PM PST
Maximum data alignment: 8
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: en_US.UTF-8
LC_CTYPE: en_US.UTF-8