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: Fix spinlock usage in UnpinBuffer()


  • From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
  • To: Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu>
  • Cc: pgsql-patches(at)postgresql(dot)org
  • Subject: Re: Fix spinlock usage in UnpinBuffer()
  • Date: Wed, 28 Dec 2005 14:56:29 -0500
  • Message-id: <21361.1135799789@sss.pgh.pa.us> <text/plain>

Qingqing Zhou <zhouqq(at)cs(dot)toronto(dot)edu> writes:
> There is no LWLock protecting the spinlock in UnpinBuffer(),

I don't believe this is necessary, and if it is necessary the patch
is wrong anyway.  Because the code uses _NoHoldoff, there won't be
any check of InterruptPending in that segment of code.  Furthermore,
any callers who don't have their own interrupt holdoff in force are
probably broken --- it's unlikely that the state of bufmgr is globally
correct if the caller of UnpinBuffer loses control.

Exactly which path of control are you worried about?

			regards, tom lane



Home | Main Index | Thread Index

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