From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Don Seiler <don@seiler.us>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Passwords in clear text in server log
Date: Wed, 11 Oct 2017 21:43:23 +0200
Message-ID: <20171011194323.s2alxtl3krdvj7hj@alvherre.pgsql> (raw)
In-Reply-To: <CAHJZqBCxQth34+KhNji4cQzy9WuNMvpWav863fNDkE0njdq02Q@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
Don Seiler wrote:
> If you're going to log statements that fail to parse, then yes it will make
> it harder to close these loopholes. That's also new to me, coming from a
> different RDBMS world. It logs neither bad (failed to parse) SQL nor user
> passwords.
Actually, I do wonder why we log statements that fail to parse. Surely
the client ought to know that it failed, but what is the value of
additionally storing the query in the server log?
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: alvherre@alvh.no-ip.org, don@seiler.us, tgl@sss.pgh.pa.us
Subject: Re: Passwords in clear text in server log
In-Reply-To: <20171011194323.s2alxtl3krdvj7hj@alvherre.pgsql>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox