| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | "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-07 13:03:05 |
| Message-ID: | 1ACF45F0-3049-44DE-96E7-FA532CB5CD54@yesql.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 7 Mar 2023, at 09:26, Daniel Gustafsson <daniel(at)yesql(dot)se> wrote:
> Right, what I meant was: can a pg_regress sql/expected test drive a psql
> interactive prompt? Your comments suggested using password.sql so I was
> curious if I was missing a neat trick for doing this.
The attached v7 adds a TAP test for verifying that \password use the changed
SCRAM iteration count setting, and dials back the other added test to use fewer
iterations than the default setting in order to shave (barely noticeable
amounts of) cpu cycles.
Running interactive tests against psql adds a fair bit of complexity and isn't
all that pleasing on the eye, but it can be cleaned up and refactored when
https://commitfest.postgresql.org/42/4228/ is committed.
--
Daniel Gustafsson
| Attachment | Content-Type | Size |
|---|---|---|
| v7-0001-Make-SCRAM-iteration-count-configurable.patch | application/octet-stream | 16.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2023-03-07 13:18:13 | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |
| Previous Message | Heikki Linnakangas | 2023-03-07 12:38:14 | Re: XID formatting and SLRU refactorings (was: Add 64-bit XIDs into PostgreSQL 15) |