Skip site navigation (1) Skip section navigation (2)

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search archives
  Advanced Search

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: Thu, 31 Jan 2008 21:41:01 -0500 (EST)
  • Message-id: <200802010241.m112f1r04410@momjian.us> <text/plain>

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. +



Home | Main Index | Thread Index

Privacy Policy | About PostgreSQL
Copyright © 1996 – 2012 PostgreSQL Global Development Group