From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ervin Weber <webervin@gmail.com>
cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Don Seiler <don@seiler.us>,
        pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Passwords in clear text in server log
In-reply-to: 
 <CAFC4ZFhLKQ49Jnt75COpK+_68v2uYUkZnDFYhbvy190EpHr_0g@mail.gmail.com>
References: 
 <CAHJZqBCxQth34+KhNji4cQzy9WuNMvpWav863fNDkE0njdq02Q@mail.gmail.com>
 <20171011194323.s2alxtl3krdvj7hj@alvherre.pgsql>
 <CAFC4ZFhLKQ49Jnt75COpK+_68v2uYUkZnDFYhbvy190EpHr_0g@mail.gmail.com>
Comments: In-reply-to Ervin Weber <webervin@gmail.com>
	message dated "Wed, 11 Oct 2017 22:46:44 +0300"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <23671.1507752070.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Wed, 11 Oct 2017 16:01:10 -0400
Message-ID: <23672.1507752070@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

Ervin Weber <webervin@gmail.com> writes:
> Alvaro Herrera  wrote:
>> 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?

> To debug clients who claim it is working on their end, but data does not =
change.

We have heard many times from people who don't have enough insight, or
enough debug support client-side, to know exactly what queries their
apps are issuing.  Disabling query logging would be a horrible setback
for debuggability of such apps.  How many times have you said "consult
the postmaster log to find out what's going on"?

			regards, tom lane


--=20
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin