Re: Is this a problem in GenericXLogFinish()? - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Is this a problem in GenericXLogFinish()?
Date
Msg-id CA+TgmobWm1oqVPP3h+DixZEs=CELhsoySr5uqPtoVNR8H0kwzw@mail.gmail.com
Whole thread Raw
In response to Re: Is this a problem in GenericXLogFinish()?  (Heikki Linnakangas <hlinnaka@iki.fi>)
List pgsql-hackers
On Wed, Oct 11, 2023 at 7:53 AM Heikki Linnakangas <hlinnaka@iki.fi> wrote:
> > + * Buffer must be pinned and exclusive-locked.  (If caller does not hold
> > + * exclusive lock, then the result may be stale before it's returned.)
> The comment suggests that you don't need to hold an exclusive lock when
> you call this, but there's an assertion that you do.

I don't think the comment suggests that. It would if you only read the
sentence in parentheses. But if you read both of them it seems clear
enough. I guess the parenthetical sentence cloud say "If the caller
did not hold an exclusive lock, then the result might become stale
even before it was returned," basically putting the whole thing in the
subjunctive.

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



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Is this a problem in GenericXLogFinish()?
Next
From: Amit Kapila
Date:
Subject: Re: Add null termination to string received in parallel apply worker