Re: [HACKERS] Log LDAP "diagnostic messages"? - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [HACKERS] Log LDAP "diagnostic messages"?
Date
Msg-id 20170816031404.ynyws75hbw35x3n2@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] Log LDAP "diagnostic messages"?  (Christoph Berg <myon@debian.org>)
Responses Re: [HACKERS] Log LDAP "diagnostic messages"?  (Ashutosh Bapat <ashutosh.bapat@enterprisedb.com>)
List pgsql-hackers
Christoph Berg wrote:
> Re: Thomas Munro 2017-08-10 <CAEepm=09jnV7hK5rTxPp816bMuve7dJGbjtEcjeXrhAELHFxqw@mail.gmail.com>
> > > Agreed.  Here's a version that skips those useless detail messages
> > > using a coding pattern I found elsewhere.
> > 
> > Rebased after bf6b9e94.
> 
> > message ? errdetail("Diagnostic message: %s", message) : 0));
> 
> "Diagnostic message" doesn't really mean anything, and printing
> "DETAIL: Diagnostic message: <something>" seems redundant to me. Maybe
> drop that prefix? It should be clear from the context that this is a
> message from the LDAP layer.

I think making it visible that the message comes from LDAP (rather than
Postgres or anything else) is valuable.  How about this?
LOG:  could not start LDAP TLS session: Protocol errorDETAIL:  LDAP diagnostics: unsupported extended operation.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] Moving relation extension locks out of heavyweight lock manager
Next
From: Rafia Sabih
Date:
Subject: Re: [HACKERS] Parallel Append implementation