From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: SR standby hangs |
Date: | 2011-02-18 22:13:34 |
Message-ID: | 4D5EEF0E.40306@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 02/18/2011 03:42 PM, Robert Haas wrote:
> On Fri, Feb 18, 2011 at 2:50 PM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas<robertmhaas(at)gmail(dot)com> writes:
>>> On Fri, Feb 18, 2011 at 2:35 PM, Andrew Dunstan<andrew(at)dunslane(dot)net> wrote:
>>>> It's not running HS, so there's no query to wait on.
>>> That seems to imply that recovery has leaked a buffer pin.
>> No, because then the sanity check in LockBufferForCleanup would have
>> fired:
>>
>> /* There should be exactly one local pin */
>> if (PrivateRefCount[buffer - 1] != 1)
>> elog(ERROR, "incorrect local pin count: %d",
>> PrivateRefCount[buffer - 1]);
> Hmm, yeah.
>
>> Some sort of deadly embrace with the bgwriter, maybe?
> Maybe.
>
> I think it'd be useful to know what the buffer header thinks the
> refcount on that buffer is, and what the startup process and the
> bgwriter each have for PrivateRefCount[buffer].
I'll see what I can find out (damn I hate driving debuggers).
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2011-02-18 22:30:13 | Re: WIP - Add ability to constrain backend temporary file space |
Previous Message | Bruce Momjian | 2011-02-18 22:10:47 | Re: DropRelFileNodeBuffers API change (was Re: [BUGS] BUG #5599: Vacuum fails due to index corruption issues) |