Re: Page-at-a-time Locking Considerations - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Page-at-a-time Locking Considerations
Date
Msg-id 5973.1202149662@sss.pgh.pa.us
Whole thread Raw
In response to Page-at-a-time Locking Considerations  (Simon Riggs <simon@2ndquadrant.com>)
Responses Re: Page-at-a-time Locking Considerations  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndquadrant.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


pgsql-hackers by date:

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