Re: Tracking down log segment corruption

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gordon Shannon <gordo169(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Tracking down log segment corruption
Date: 2010-05-02 18:52:18
Message-ID: 15061.1272826338@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Gordon Shannon <gordo169(at)gmail(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Ivan Voras 2010-05-02 19:19:32 Re: File compression in WinXP
Previous Message Tom Lane 2010-05-02 18:41:58 Re: postgres crashes - could not reattach to shared memory