From: | feichanghong <feichanghong(at)qq(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, andres <andres(at)anarazel(dot)de>, "sawada(dot)mshk" <sawada(dot)mshk(at)gmail(dot)com>, "horikyota(dot)ntt" <horikyota(dot)ntt(at)gmail(dot)com> |
Subject: | Re: ReplicationSlotRelease may set the statusFlags of other processes in PG14 |
Date: | 2024-03-27 06:53:55 |
Message-ID: | tencent_439D191F64260D1C7108474A73EFD4194108@qq.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Dear Michael,
Thank you for your attention.
> On Mar 19, 2024, at 11:57, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> Yeah, that's something that we had better fix in all stable branches.
Yes, as I mentioned in my last reply, it is only necessary to fix the issue in V14.
> The asserts would offer some protection moving on, but I would take
> the safer move of only adding a protection like what you are
> suggestion on HEAD and not in stable branches, just in case we're
> missing something around them.
I agree it, we may only need to add assert checks on HEAD.
Best Regards,
Fei Changhong
Alibaba Cloud Computing Ltd.
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2024-03-27 07:42:21 | Re: BUG #18379: LDAP bind password exposed |
Previous Message | feichanghong | 2024-03-27 06:43:15 | Re: MarkBufferDirty Assert held LW_EXCLUSIVE lock fail when ginFinishSplit |