Postgres Pro
Downloads
Home   >   mailing lists

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

From Nazir Bilal Yavuz
Subject Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?
Date
Msg-id CAN55FZ0TEDthuRD=TEYLbDr69iUsLwdQJB34S0BCyz1zzXTceg@mail.gmail.com
Whole thread Raw
In response to Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?  (Srinath Reddy Sadipiralla <srinath.reddy@zohocorp.com>)
Responses Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?
Re: Why we need to check for local buffers in BufferIsExclusiveLocked and BufferIsDirty?
List pgsql-hackers
Tree view 
Hi Srinath,

On Sat, 7 Dec 2024 at 11:17, Srinath Reddy Sadipiralla
<srinath.reddy@zohocorp.com> wrote:
> > ---- On Fri, 06 Dec 2024 16:40:51 +0530 Nazir Bilal Yavuz <byavuz81@gmail.com> wrote ---
> > LGTM.
>
> sorry i didn't get,what you meant to say is the assert failure which i said is correct and does my patch to this
looksgood?🤔 

Sorry if I was not clear. Yes, I wanted to say what you said is
correct and the patch looks good to me.

--
Regards,
Nazir Bilal Yavuz
Microsoft

pgsql-hackers by date:

Previous
From: Egor Rogov
Date:
Subject: Exposing index AM properties at SQL level
Next
From: Evgeny
Date:
Subject: Re: [PATCH] Support Int64 GUCs