From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
Cc: | Alexey Bashtanov <bashtanov(at)imap(dot)cc>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: log bind parameter values on error |
Date: | 2019-12-05 18:33:36 |
Message-ID: | 20191205183336.GA30063@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hello
On 2019-Dec-05, Andres Freund wrote:
> On 2019-12-05 14:19:45 -0300, Alvaro Herrera wrote:
> > What this does is set an error callback, which adds the parameter values
> > in the DETAIL line. This is at odds with all existing error callbacks:
> > they only add stuff to the CONTEXT string. The implication is that
> > if an error site has a direct errdetail_log() and is run under this
> > error stack, that site's detail is going to be lost and replaced by the
> > "params" one. Currently there aren't many errdetail_log() lines, so it
> > doesn't seem like a terrible problem. However, it's something to keep
> > in mind.
>
> It'd not be too hard avoiding overwriting if we wanted.
Hmm, maybe errdetail_log() ought to do that. However: if some place has
errdetail() and then this introduces errdetail_log(), then the former is
not included in the server log (only in the client log).
> Makes me wonder though, if we ought to invent something similar to the
> errdata fields we have for schema, table, etc...
Hmm, perhaps we should do that. It avoids the problem altogether.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-12-05 18:41:20 | Re: [Proposal] Level4 Warnings show many shadow vars |
Previous Message | Bruce Momjian | 2019-12-05 18:12:17 | Re: Append with naive multiplexing of FDWs |