| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ervin Weber <webervin(at)gmail(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Don Seiler <don(at)seiler(dot)us>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Passwords in clear text in server log |
| Date: | 2017-10-11 20:01:10 |
| Message-ID: | 23672.1507752070@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ervin Weber <webervin(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Don Seiler | 2017-10-11 20:09:51 | Re: Passwords in clear text in server log |
| Previous Message | Ervin Weber | 2017-10-11 19:46:44 | Re: Passwords in clear text in server log |