Why was my message flagged via fraud detection? What do I need to do to prevent that so I can reply?
We have several email aliases at my work location: awilliams@teamdrg.com , awilliams@dresources.com and awilliams@dresourcesgroup.com – I believe my outlook client was reconfigured recently to use @teamdrg.com, but I have posted here before, but I think that was using @dresources.com
Thanks,
Alex
From: pgsql-admin-owner@postgresql.org [mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Williams, Alex Sent: Wednesday, October 11, 2017 4:18 PM To: Tom Lane <tgl@sss.pgh.pa.us>; 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: [ADMIN] Passwords in clear text in server log
This sender failed our fraud detection checks and may not be who they appear to be. Learn about spoofing
"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"?"
I completely agree. There are many cases, not just edge cases, where this has been vital to isolate and resolve issues.
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"?