| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: SR standby hangs |
| Date: | 2011-02-18 19:50:12 |
| Message-ID: | 13876.1298058612@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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]);
Some sort of deadly embrace with the bgwriter, maybe?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2011-02-18 19:57:11 | Re: Snapshot synchronization, again... |
| Previous Message | Josh Berkus | 2011-02-18 19:48:24 | Re: WIP - Add ability to constrain backend temporary file space |