Re: Buffer Cache Problem

From: jacktby jacktby <jacktby(at)gmail(dot)com>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Buffer Cache Problem
Date: 2023-11-10 14:38:57
Message-ID: 8ADBC847-2D66-4EFB-89AF-76338B8B46F4@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> 2023年11月10日 22:31,jacktby jacktby <jacktby(at)gmail(dot)com> 写道:
>
> 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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message jian he 2023-11-10 14:59:27 Re: EXCLUDE COLLATE in CREATE/ALTER TABLE document
Previous Message jacktby jacktby 2023-11-10 14:31:40 Re: Buffer Cache Problem