Re: Raising the SCRAM iteration count - Mailing list pgsql-hackers

From Daniel Gustafsson
Subject Re: Raising the SCRAM iteration count
Date
Msg-id 271710AC-D588-4060-9898-F85C719C4D7D@yesql.se
Whole thread Raw
In response to Re: Raising the SCRAM iteration count  (Michael Paquier <michael@paquier.xyz>)
Responses Re: Raising the SCRAM iteration count  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
> On 24 Mar 2023, at 00:33, Michael Paquier <michael@paquier.xyz> wrote:
>
> On Thu, Mar 23, 2023 at 10:46:56PM +0100, Daniel Gustafsson wrote:
>> I'm fairly convinced it's a timeout in the interactive psql session.  Given how
>> ugly the use of that is I'm sort of waiting for Andres' refactoring patch [0] to
>> commit this such that I can rewrite the test in a saner and more robust way.
>
> FWIW, I'd be OK here even if you don't have a test for libpq in the
> first change as what you have sent is already testing for the core
> machinery in scram-common.c.  You could always add one later.

Yeah, that's my fallback in case we are unable to get the TAP refactoring done
in time for the end of the CF/feature freeze.

I've actually ripped out the test in question in the attached v9 to have it
ready and building green in CFbot.

--
Daniel Gustafsson


Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: fix a typo in file src/backend/utils/adt/xid8funcs.c comment
Next
From: "wangw.fnst@fujitsu.com"
Date:
Subject: RE: Data is copied twice when specifying both child and parent table in publication