Re: Tracking down log segment corruption - Mailing list pgsql-general

From Tom Lane
Subject Re: Tracking down log segment corruption
Date
Msg-id 15061.1272826338@sss.pgh.pa.us
Whole thread Raw
In response to Re: Tracking down log segment corruption  (Gordon Shannon <gordo169@gmail.com>)
Responses Re: Tracking down log segment corruption  (Gordon Shannon <gordo169@gmail.com>)
List pgsql-general
Gordon Shannon <gordo169@gmail.com> writes:
> Bingo.  Yes it is reasonable.  It was 25 seconds between my altering the
> index in question and the server crash.

Sounds like we have a smoking gun.  Could you show all your non-default
postgresql.conf settings on the master?  I'm wondering about
full_page_writes in particular, but might as well gather all the
relevant data while we're at it.  Easiest way is:

select name,setting from pg_settings where source not in ('default','override');

            regards, tom lane

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: postgres crashes - could not reattach to shared memory
Next
From: Ivan Voras
Date:
Subject: Re: File compression in WinXP