Re: Extension Enhancement: Buffer Invalidation in pg_buffercache - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: Extension Enhancement: Buffer Invalidation in pg_buffercache
Date
Msg-id CA+hUKG+rBfs9GtsNCrbosNNiQKY94L61UuqraH6EvEUCfe_8Jg@mail.gmail.com
Whole thread Raw
In response to Re: Extension Enhancement: Buffer Invalidation in pg_buffercache  (Andres Freund <andres@anarazel.de>)
List pgsql-hackers
On Mon, Apr 8, 2024 at 12:10 PM Andres Freund <andres@anarazel.de> wrote:
> On 2024-04-07 11:07:58 +1200, Thomas Munro wrote:
> > I thought of a better name for the bufmgr.c function though:
> > InvalidateUnpinnedBuffer().  That name seemed better to me after I
> > festooned it with warnings about why exactly it's inherently racy and
> > only for testing use.
>
> I still dislike that, fwiw, due to the naming similarity to
> InvalidateBuffer(), which throws away dirty buffer contents too. Which
> obviously isn't acceptable from "userspace".  I'd just name it
> pg_buffercache_evict() - given that the commit message's first paragraph uses
> "it is useful to be able to evict arbitrary blocks" that seems to describe
> things at least as well as "invalidate"?

Alright, sold.  I'll go with EvictUnpinnedBuffer() in bufmgr.c and
pg_buffercache_evict() in the contrib module.



pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: [MASSMAIL]Replace FunctionCall2Coll with FunctionCallInvoke
Next
From: Amit Kapila
Date:
Subject: Re: Synchronizing slots from primary to standby