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-08 01:13:59 |
Message-ID: | CA+TgmoaiK47Ee7ZvaT4f_TbQk7y3UEo5_PraceMHjo8mAtSKqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Thu, Jul 7, 2022 at 8:22 PM Kyotaro Horiguchi
<horikyota(dot)ntt(at)gmail(dot)com> wrote:
> Thanks for the reply.
>
> Yes if it is "RelFileLocator when we're talking about all the things
> that are needed to locate a relation's files on disk,". I read this as
> RelFileLocator is a kind of pointer to files. I thought RelFileNode
> as a pointer as well as the storage itself. The difference of the two
> for me could be analogized as the difference between "DropFileBuffers"
> and "DropFileNameBuffers". I think the latter is usually spelled as
> "DropBuffersByFileNames" or such.
>
> Though, I don't want to keep fighting any further if others don't feel
> it uneasy ;)
I wouldn't mind if we took "Locator" out of the name of that function
and just called it DropRelFileBuffers or DropRelationBuffers or
something. That would be shorter, and maybe more intuitive.
I wasn't quite able to understand whether your original question was
prompted by having missed the commit in question, or whether you
disagreed with it, so that's why I asked whether you had seen the
commit message.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2022-07-08 01:14:25 | Re: [BUG] Logical replication failure "ERROR: could not map filenode "base/13237/442428" to relation OID" with catalog modifying txns |
Previous Message | Kyotaro Horiguchi | 2022-07-08 00:44:10 | Re: Add a test for "cannot truncate foreign table" |