Re: DropRelFileLocatorBuffers

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: DropRelFileLocatorBuffers
Date: 2022-07-07 12:36:14
Message-ID: CA+TgmoYR77OjL_V9Q0wQNN_BwxdfgkVDGXE30JhEVo+MUmQ5FA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Jul 7, 2022 at 4:44 AM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> While working on a patch, I met a function with the signature of:
>
> > DropRelFileLocatorBuffers(SMgrRelation smgr_reln, ForkNumber *forkNum,
> > int nforks, BlockNumber *firstDelBlock)
>
> It was DropRelFileNodeBuffers(), which means "Drop buffers for a
> RelFileNode", where RelFileNode means a storage or a (set of) file(s).
> In that sense, "Drop buffers for a RelFile*Locator*" sounds a bit off
> to me. Isn't it better change the name? RelFileLocator doesn't look
> to be fit here.
>
> "DropRelFileBuffers" works better at least for me.. If it does, some
> other functions need the same amendment.

Have you looked at the commit message for
https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=b0a55e43299c4ea2a9a8c757f9c26352407d0ccc
?

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Zhao Rui 2022-07-07 12:41:37 Re:Improving RLS planning
Previous Message Pavel Stehule 2022-07-07 12:30:10 Re: Schema variables - new implementation for Postgres 15