From: | Robert Sjöblom <robert(dot)sjoblom(at)fortnox(dot)se> |
---|---|
To: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18802: password field in log |
Date: | 2025-02-11 08:30:45 |
Message-ID: | f05e40b5-81f7-4726-8691-ea3c3855ae96@fortnox.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2025-02-11 09:14, PG Bug reporting form wrote:
> The following bug has been logged on the website:
>
> Bug reference: 18802
> Logged by: roseduan
> Email address: roseduan7(at)163(dot)com
> PostgreSQL version: 17.2
> Operating system: CentOS
> Description:
>
> set log_statement to "all";
>
> create user some_user password '123456';
>
> And then I found that the password will show in the log file, is this an
> expected behavior?
>
Yes, this is the expected behavior; there are several threads about this
on the various mailing lists, here's the first I fond:
https://www.postgresql.org/message-id/CAHJZqBDe1-oiYtdh5pcWLAhr3jsDMFQg4miv3PYADH3YWKqZ2w%40mail.gmail.com
A solution is to override the log statement while setting the password:
BEGIN;
SET LOCAL log_statement = 'none';
ALTER USER ... SET PASSWORD ...;
COMMIT;
Another would be to prepare the digest client-side instead, and use
\password in psql.
Best regards,
Robert Sjöblom
--
Innehållet i detta e-postmeddelande är konfidentiellt och avsett endast för
adressaten.Varje spridning, kopiering eller utnyttjande av innehållet är
förbjuden utan tillåtelse av avsändaren. Om detta meddelande av misstag
gått till fel adressat vänligen radera det ursprungliga meddelandet och
underrätta avsändaren via e-post
From | Date | Subject | |
---|---|---|---|
Next Message | Virender Singla | 2025-02-11 10:02:42 | Major Version Upgrade failure due to orphan roles entries in catalog |
Previous Message | PG Bug reporting form | 2025-02-11 08:14:37 | BUG #18802: password field in log |