Re: pgsql: Add checks to TRUNCATE, CLUSTER, and REINDEX to prevent

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Gregory Stark <stark(at)enterprisedb(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-committers(at)postgresql(dot)org
Subject: Re: pgsql: Add checks to TRUNCATE, CLUSTER, and REINDEX to prevent
Date: 2008-02-01 02:41:01
Message-ID: 200802010241.m112f1r04410@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Gregory Stark wrote:
> "Bruce Momjian" <bruce(at)momjian(dot)us> writes:
>
> > * Improve deadlock detection when deleting items from shared buffers
> >...
> > Let me know if there is better wording.
>
> I'm not sure whhere deleting items from shared buffers enters into it.
>
> I think you need something like:
>
> Add deadlock detection when a process holding a buffer pin is blocked by a
> lock held by a process attempting to LockBufferForCleanup() on that buffer or
> more complex versions thereof. (And without adding unacceptable overhead to
> pin/unpin.)

Text updated:

* Improve deadlock detection when a page cleaning lock conflicts
with a shared buffer that is pinned

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Bruce Momjian 2008-02-01 02:41:10 pgsql: Update item: < * Improve deadlock detection when deleting items
Previous Message Bruce Momjian 2008-01-31 23:31:33 pgsql: Fix spelling typo in comment.