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

From Simon Riggs
Subject Re: Page-at-a-time Locking Considerations
Date
Msg-id 1202158470.4252.597.camel@ebony.site
Whole thread Raw
In response to Re: Page-at-a-time Locking Considerations  (Gregory Stark <stark@enterprisedb.com>)
Responses Re: Page-at-a-time Locking Considerations  (Alvaro Herrera <alvherre@commandprompt.com>)
Re: Page-at-a-time Locking Considerations  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
On Mon, 2008-02-04 at 20:03 +0000, Gregory Stark wrote:

> I wonder how hard it would be to shove the clog into regular shared
> memory pages and let the clock sweep take care of adjusting the
> percentage of shared mem allocated to the clog versus data pages.

There is a reason that's not been done... try it and see.

Plus it doesn't fully resolve the main issue as described.

--  Simon Riggs 2ndQuadrant  http://www.2ndQuadrant.com 



pgsql-hackers by date:

Previous
From: "Heikki Linnakangas"
Date:
Subject: Re: FW: bitemporal functionality for PostgreSQL
Next
From: Tom Lane
Date:
Subject: Re: Page-at-a-time Locking Considerations