Re: WIP: dynahash replacement for buffer table

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Ryan Johnson <ryan(dot)johnson(at)cs(dot)utoronto(dot)ca>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: WIP: dynahash replacement for buffer table
Date: 2014-10-16 18:36:35
Message-ID: CA+TgmoZ6k1BKenaf3n-gYZoAhxRG2P3A4sVqmLAHswyd+-cwsA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 16, 2014 at 12:26 PM, Ryan Johnson
<ryan(dot)johnson(at)cs(dot)utoronto(dot)ca> wrote:
> The only metric where RCU loses to
> hazard pointers is if you have really tight timing constraints on resource
> reclamation.

I think we do have that problem. It's certainly completely
unacceptable for a query to prevent buffer reclaim on any significant
number of buffers even until the end of the query, let alone the end
of the transaction.

But, hey, if somebody wants to try writing a patch different than the
one that I wrote and see whether it works better than mine, I'm
totally cool with that. This is something I came up with, and we're
here to evaluate whether it works better than any other option that we
have now or that someone wants to develop. I'm not saying this is the
best solution; it's just something I've got that seems to basically
work.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2014-10-16 18:39:09 Re: UPSERT wiki page, and SQL MERGE syntax
Previous Message Peter Geoghegan 2014-10-16 18:32:05 Re: UPSERT wiki page, and SQL MERGE syntax