Re: Add a warning message when using unencrypted passwords

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Jelte Fennema-Nio <postgres(at)jeltef(dot)nl>
Cc: Guillaume Lelarge <guillaume(at)lelarge(dot)info>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Add a warning message when using unencrypted passwords
Date: 2024-12-09 13:26:05
Message-ID: CAKAnmm+J6=qrJA3tTwt-GH2H3eNPpXW3AX8g9Q3VNnk2WgJCNw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Overall +1 to the idea of a warning.

Regarding warning vs error, I agree that a WARNING is probably the right
> choice generally. But I think that Divya is correct: When
> log_statement = 'all', an error should be thrown instead.

First, it should be for 'all' AND 'ddl'. And obviously glossing over
log_min_duration_statement entirely. But -1 to throwing an ERROR - that's
not really an error, and not our call to make, so a WARNING is sufficient.

Cheers,
Greg

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Yan Chengpeng 2024-12-09 13:27:49 Re: [PATCH] Fix jsonb comparison for raw scalar pseudo arrays
Previous Message Bertrand Drouvot 2024-12-09 13:25:54 Re: Track the amount of time waiting due to cost_delay