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

From: Greg Sabino Mullane <greg(at)endpoint(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org, Jeff Frost <jeff(at)pgexperts(dot)com>
Subject: Re: Backends stalled in 'startup' state: index corruption
Date: 2012-05-26 17:26:38
Message-ID: 20120526172638.GE10277@tinybird.home
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, May 26, 2012 at 01:25:29PM -0400, Tom Lane wrote:
> Greg Sabino Mullane <greg(at)endpoint(dot)com> writes:
> > On Sat, May 26, 2012 at 12:17:04PM -0400, Tom Lane wrote:
> >> If you see any block numbers above about 20 then maybe the triggering
> >> condition is a row relocation after all.
>
> > Highest was 13.
>
> Hm ... but wait, you said you'd done a VACUUM FULL on the catalogs.
> So it's not clear whether this is reflective of the state at the time
> the problem was happening.

True. I'll try to get a high water mark when (er...if!) it happens again.

--
Greg Sabino Mullane greg(at)endpoint(dot)com
End Point Corporation
PGP Key: 0x14964AC8

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Jan-Benedict Glaw 2012-05-26 18:57:41 Re: VIP: new format for psql - shell - simple using psql in shell
Previous Message Tom Lane 2012-05-26 17:25:29 Re: Backends stalled in 'startup' state: index corruption