Re: Raising the SCRAM iteration count

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: "Gregory Stark (as CFM)" <stark(dot)cfm(at)gmail(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Raising the SCRAM iteration count
Date: 2023-03-23 21:46:56
Message-ID: E63671CA-83E2-47EF-AE3E-9640DD98D686@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 22 Mar 2023, at 04:14, Gregory Stark (as CFM) <stark(dot)cfm(at)gmail(dot)com> wrote:
> On Tue, 14 Mar 2023 at 14:54, Gregory Stark (as CFM)
> <stark(dot)cfm(at)gmail(dot)com> wrote:
>>
>> CFBot is failing with this test failure... I'm not sure if this just
>> represents a timing dependency or a bad test or what?
>
> CFBot is now consistently showing these test failures. I think there
> might actually be a problem here?

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.

--
Daniel Gustafsson

[0] https://commitfest.postgresql.org/42/4228/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Thomas Munro 2023-03-23 22:00:40 Re: Orphaned wait event
Previous Message Euler Taveira 2023-03-23 21:40:26 Re: add log messages when replication slots become active and inactive (was Re: Is it worth adding ReplicationSlot active_pid to ReplicationSlotPersistentData?)