Re: Add a warning message when using unencrypted passwords - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: Add a warning message when using unencrypted passwords
Date
Msg-id CAKAnmm+J6=qrJA3tTwt-GH2H3eNPpXW3AX8g9Q3VNnk2WgJCNw@mail.gmail.com
Whole thread Raw
In response to Re: Add a warning message when using unencrypted passwords  (Jelte Fennema-Nio <postgres@jeltef.nl>)
Responses Re: Add a warning message when using unencrypted passwords
List 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

pgsql-hackers by date:

Previous
From: Bertrand Drouvot
Date:
Subject: Re: Track the amount of time waiting due to cost_delay
Next
From: Thomas Munro
Date:
Subject: Re: Giving the shared catalogues a defined encoding