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

From Jeff Davis
Subject Re: Is this a problem in GenericXLogFinish()?
Date
Msg-id 23d87b531fab74e69fd753791a7e5047f17da9ab.camel@j-davis.com
Whole thread Raw
In response to Re: Is this a problem in GenericXLogFinish()?  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Is this a problem in GenericXLogFinish()?
List pgsql-hackers
On Mon, 2023-10-23 at 10:14 -0400, Robert Haas wrote:
> I think that would be a bug. I think it would be OK to just change
> the
> page LSN and nothing else, but that requires calling
> MarkBufferDirty()
> at some point. If you only call PageSetLSN() and never
> MarkBufferDirty(), that sounds messed up: either the former should be
> skipped, or the latter should be added. We shouldn't modify a shared
> buffer without marking it dirty.
>

In that case, I think REGBUF_NO_CHANGE is the right name for the flag.

Committed.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Show version of OpenSSL in ./configure output
Next
From: Jeff Davis
Date:
Subject: Re: run pgindent on a regular basis / scripted manner