Re: Page-at-a-time Locking Considerations

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Page-at-a-time Locking Considerations
Date: 2008-02-04 18:27:42
Message-ID: 5973.1202149662@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndquadrant(dot)com> writes:
> In heapgetpage() we hold the buffer locked while we look for visible
> tuples.

It's a share lock though. Do you have any direct proof that this
behavior is as nasty as you claim?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2008-02-04 18:45:23 Re: Page-at-a-time Locking Considerations
Previous Message Tom Lane 2008-02-04 18:18:23 Re: [COMMITTERS] pgsql: configure tag'd 8.3.0 and built witih autoconf 2.59