Re: Atomics in localbuf.c - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Atomics in localbuf.c
Date
Msg-id 20200306190641.ak432cz2vbhurtvy@alap3.anarazel.de
Whole thread Raw
In response to Re: Atomics in localbuf.c  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Atomics in localbuf.c  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

On 2020-03-06 11:26:41 -0500, Robert Haas wrote:
> On Fri, Mar 6, 2020 at 2:04 AM Antonin Houska <ah@cybertec.at> wrote:
> > ok. What I missed is that BufferDesc.state is declared as pg_atomic_uint32
> > rather than plain int, so the pg_atomic_...() functions should be used
> > regardless the buffer is shared or local. Sorry for the noise.
>
> Right. I thought, though, that your question was why we did it that
> way instead of just declaring them as uint32. I'm not sure it's very
> important, but I think that question hasn't really been answered.

I tried, at least:

> Since local/shared buffers share the buffer header definition, we still have to use proper functions to access
> the atomic variables.

There's only one struct BufferDesc. We could separate them out /
introduce a union or such. But that'd add some complexity / potential
for mistakes too.

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: [HACKERS] [WIP] Effective storage of duplicates in B-tree index.
Next
From: Aleksei Ivanov
Date:
Subject: Re: Proposal: PqSendBuffer removal