Postgres Pro
Downloads
Home   >   mailing lists

Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty? - Mailing list pgsql-hackers

From Srinath Reddy
Subject Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?
Date
Msg-id CAFC+b6pCAsRPA15REBSnUeOf=rB4CN0VGczKY0_ii4a2N9XENQ@mail.gmail.com
Whole thread Raw
In response to Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?  (Srinath Reddy <srinath2133@gmail.com>)
List pgsql-hackers
Tree view


On Sun, Jan 26, 2025 at 10:24 PM Srinath Reddy <srinath2133@gmail.com> wrote:

as there was repeated code between BufferIsExclusiveLocked and BufferIsDirty to check if buffer is pinned and its locked exclusively,i thought it would be nice to move that repeated code into BufferIsExclusiveLocked and as we need bufHdr in BufferIsDirty which is assigned in BufferIsExclusiveLocked,so I had to change the signature of BufferIsExclusiveLocked by adding (BufferDesc **bufHdr).

Hi Tom,
if this is not the answer you are expecting ,please let me know.I am open for suggestions.

Regards, 

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Back patch of Remove durable_rename_excl()
Next
From: Bertrand Drouvot
Date:
Subject: Re: Reorder shutdown sequence, to flush pgstats later