Tom Lane wrote:
> Bricklen Anderson <BAnderson@PresiNET.com> writes:
>
>>Feb 1 11:17:50 dev94 postgres[4959]: [472-1] 2005-02-01 11:17:50 PST> ERROR: xlog flush request
>>972/FC932854 is not satisfied --- flushed only to 73/86D2640
>
>
> Hmm, have you perhaps played any games with pg_resetxlog in this database?
>
> I would have suggested that maybe this represented on-disk data
> corruption, but the appearance of two different but not-too-far-apart
> WAL offsets in two different pages suggests that indeed the end of WAL
> was up around segment 972 or 973 at one time. And now it's evidently
> ending at 73. Not good. What file names do you see in pg_xlog/, and
> what does pg_controldata show?
>
> regards, tom lane
Hi Tom,
Nope, never touched pg_resetxlog.
My pg_xlog list ranges from 000000010000007300000041 to 0000000100000073000000FE, with no breaks.
There are also these: 000000010000007400000000 to 00000001000000740000000B
$ pg_controldata
pg_control version number: 74
Catalog version number: 200411041
Database system identifier: 4738750823096876774
Database cluster state: in production
pg_control last modified: Wed 02 Feb 2005 12:38:22 AM PST
Current log file ID: 115
Next log file segment: 66
Latest checkpoint location: 73/419A4BDC
Prior checkpoint location: 73/419A4B80
Latest checkpoint's REDO location: 73/419A4BDC
Latest checkpoint's UNDO location: 0/0
Latest checkpoint's TimeLineID: 1
Latest checkpoint's NextXID: 4161807
Latest checkpoint's NextOID: 176864
Time of latest checkpoint: Wed 02 Feb 2005 12:38:22 AM PST
Database block size: 8192
Blocks per segment of large relation: 131072
Bytes per WAL segment: 16777216
Maximum length of identifiers: 64
Maximum number of function arguments: 32
Date/time type storage: floating-point numbers
Maximum length of locale name: 128
LC_COLLATE: en_CA
LC_CTYPE: en_CA
