Re: scram_iterations is undocumented GUC_REPORT
Daniel Gustafsson <daniel@yesql.se>
From: Daniel Gustafsson <daniel@yesql.se>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>,
Pg Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2024-01-30T15:08:09Z
Lists: pgsql-hackers
> On 30 Jan 2024, at 15:36, Tom Lane <tgl@sss.pgh.pa.us> wrote: > > Alvaro Herrera <alvherre@alvh.no-ip.org> writes: >> I noticed while answering a question that commit b577743000cd added the >> GUC scram_iterations and marked it GUC_REPORT, but failed to add it to >> the PQparameterStatus documentation. > > Why is it GUC_REPORT at all? I don't see a strong need for that. > (In particular, the report would be delivered too late to be of any > use in client authentication.) It's needed by PQencryptPasswordConn. -- Daniel Gustafsson
Commits
-
Update PQparameterStatus and ParameterStatus docs
- a39f1a365a3b 17.0 landed
- 17f319659930 16.3 landed
-
Make SCRAM iteration count configurable
- b577743000cd 16.0 cited