On 04/27/12 12:17, Tom Lane wrote:
> Jeff Frost <jeff(at)pgexperts(dot)com> writes:
>> Alright, found one that's a little different (at least it wasn't in InitPostgres):
> It's still blocking at bufmgr.c:531 though ... so AFAICS this is another
> victim of somebody monopolizing a buffer mapping lock.
>
>
Any idea what I should be looking for in the backtraces?
I would imagine I can ignore any that are in InitPostgres, but that still
leaves quite a few to look through.