public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bowen Shi <[email protected]>
To: Michael Paquier <[email protected]>
Cc: Aleksander Alekseev <[email protected]>
Cc: Postgres hackers <[email protected]>
Cc: Daniel Gustafsson <[email protected]>
Cc: Tom Lane <[email protected]>
Subject: Re: [PATCH] Add CHECK_FOR_INTERRUPTS in scram_SaltedPassword loop.
Date: Mon, 27 Nov 2023 11:56:31 +0800
Message-ID: <CAM_vCudfWMoYu0RhLhsksq3v71uwrvck1oMUNqxipR38GCDCbA@mail.gmail.com> (raw)
In-Reply-To: <[email protected]>
References: <CAM_vCueV6xfr08KczfaCEk5J_qeTZtgqN7+orkNLx=g+phE82Q@mail.gmail.com>
<CAJ7c6TMdDdC5f1qmS=UVx22Bvjqz=PhY=aeefwoXxGc_bK+WKQ@mail.gmail.com>
<[email protected]>
<[email protected]>
<CAM_vCufzLucPevjOC90cVD_AsPtpPHRLY2w+Zm985B-6JHxz1w@mail.gmail.com>
<CAJ7c6TMLeqc6MR76LaJCk3jeBnnX=tuVUE=yv9+k7tkCb-OeYg@mail.gmail.com>
<[email protected]>
> I think that we should backpatch that down to v16 at least where the
> GUC has been introduced as it's more like a nuisance if one sets the
> GUC to an incorrect value, and I'd like to apply the patch this way.
Agreed.
The patch has been submitted in https://commitfest.postgresql.org/46/4671/
Regards
Bowen Shi
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: [PATCH] Add CHECK_FOR_INTERRUPTS in scram_SaltedPassword loop.
In-Reply-To: <CAM_vCudfWMoYu0RhLhsksq3v71uwrvck1oMUNqxipR38GCDCbA@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox