| From: | Don Seiler <don(at)seiler(dot)us> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Ervin Weber <webervin(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Passwords in clear text in server log |
| Date: | 2017-10-11 20:09:51 |
| Message-ID: | CAHJZqBBuYaT5YTv_EaiB_b4-HA8y84eahJbfKfmtpGDfVP6RkQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Oct 11, 2017 at 3:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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"?
>
Not logging statements that fail to parse isn't the same as disabling query
logging. If a statement fails to parse it can't really be considered a
query in my opinion. When it fails to parse it *should* send a
loud-and-clear error to whatever client-side application sent it. Granted a
lazy developer could code their app to swallow all errors, but then I'd say
they deserve the headache.
--
Don Seiler
www.seiler.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Williams, Alex | 2017-10-11 20:17:37 | Re: Passwords in clear text in server log |
| Previous Message | Tom Lane | 2017-10-11 20:01:10 | Re: Passwords in clear text in server log |