Re: Backends stalled in 'startup' state: index corruption

From: Jeff Frost <jeff(at)pgexperts(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Greg Sabino Mullane <greg(at)endpoint(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Backends stalled in 'startup' state: index corruption
Date: 2012-05-26 04:13:44
Message-ID: 7DE4C507-4D34-4BE9-8D4D-617894EBC64F@pgexperts.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On May 25, 2012, at 7:12 PM, Tom Lane wrote:

> Jeff Frost <jeff(at)pgexperts(dot)com> writes:
>> In our customer's case, the size of pg_attribute was a little less than 1/4 of shared_buffers, so might not be the syncscan?
>
> Could you go back and double check that? If the shared_buffers setting
> were 7GB not 8GB,

It definitely started happening with 8GB of shared_buffers.

We actually tried reducing shared_buffers to 2GB to see if we were writing out too many dirty buffers at checkpoint time or something, but that had no effect, so we put it back to 8GB.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2012-05-26 04:18:54 Re: Per-Database Roles
Previous Message Bruce Momjian 2012-05-26 03:12:45 Re: Per-Database Roles