Re: hung backends stuck in spinlock heavy endless loop - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: hung backends stuck in spinlock heavy endless loop
Date
Msg-id CAM3SWZRYkZVm7Nkyo1gkqpYm_7Sb5WH6Ui2SD92yxr58=cgi5w@mail.gmail.com
Whole thread Raw
In response to Re: hung backends stuck in spinlock heavy endless loop  (Peter Geoghegan <pg@heroku.com>)
Responses Re: hung backends stuck in spinlock heavy endless loop
List pgsql-hackers
On Wed, Jan 14, 2015 at 5:23 PM, Peter Geoghegan <pg@heroku.com> wrote:
> My immediate observation here is that blocks 2 and 9 have identical
> metadata (from their page opaque area), but partially non-matching
> data items (however, the number of items on each block is consistent
> and correct according to that metadata, as far as it goes). I think
> block 9 is supposed to have a right-link to block 5 (block 5 seems to
> think so, at least -- its left link is 9).

I am mistaken on one detail here - blocks 2 and 9 are actually fully
identical. I still have no idea why, though.
-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Enforce creation of destination folders for source files in pg_regress (Was: pg_regress writes into source tree)
Next
From: Amit Kapila
Date:
Subject: Re: Merging postgresql.conf and postgresql.auto.conf