> Of course, we could create login credentials, login configuration options > for every DBA colleagues. But, as I said previous that big problem is > "PostgreSQL logs include changing passwords on clear-text not encrypted" No, the big problem is that you don't consider your fellow DBA's reliable. That's a problem you need to solve rather sooner than later. Another problem is that you are apparently logging all SQL statements. Not only does that store the SQL for changing database users, it will also slow down your database. You should really only log all statements if you're debugging something, and only temporarily. Of course it would be nice if those passwords would be encrypted, but they are simply part of SQL statements - there is no means in SQL to distinguish a password string literal from any other type of literal, until the statement hits the database. -- If you can't see the forest for the trees, Cut the trees and you'll see there is no forest. -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
