Re: errbacktrace
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>,
Alvaro Herrera <alvherre@2ndquadrant.com>,
Dmitry Dolgov <9erthalion6@gmail.com>,
Thomas Munro <thomas.munro@gmail.com>
Date: 2019-08-13T14:14:51Z
Lists: pgsql-hackers
Peter Eisentraut <peter.eisentraut@2ndquadrant.com> writes: > I have changed the configuration setting to backtrace_functions plural, > so that you can debug more than one location at once. I had originally > wanted to do that but using existing functions like > SplitIdentifierString() resulted in lots of complications with error > handling (inside error handling!). So here I just hand-coded the list > splitting. Seems simple enough. I think it's a pretty bad idea for anything invocable from elog to trample on the process-wide strtok() state. Even if there's no conflict today, there will be one eventually, unless you are going to adopt the position that nobody else is allowed to use strtok(). regards, tom lane
Commits
-
Remove debugging aid
- 45ff049e288b 13.0 landed