public inbox for [email protected]
help / color / mirror / Atom feedFrom: jacktby jacktby <[email protected]>
To: [email protected]
Subject: Re: Buffer Cache Problem
Date: Fri, 10 Nov 2023 22:38:57 +0800
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<CAEze2WjGH6ccJW1Jv+JLhn=uFec8HAZCOJikbzHQifQMaR9dpw@mail.gmail.com>
<[email protected]>
> 2023年11月10日 22:31，jacktby jacktby <[email protected]> 写道：
>
> In the bus_internal.h,I see
> ====================================================
> Note: Buffer header lock (BM_LOCKED flag) must be held to examine or change tag, state or wait_backend_pgprocno fields.
> ====================================================
> As we all know, this buffer header lock is implemented by a bit in state filed, and this state field is a atomic_u32 type, so in fact we don’t need to
> hold buffer lock when we update state, this comment has error，right?
Oh, sorry this is true, in fact we never acquire a spin lock when update the state.
view thread (3+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected]
Subject: Re: Buffer Cache Problem
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox