On 2018-04-10 23:32, Alvaro Herrera wrote:
> To figure out, I used the attached patch (not intended for application)
> to add a backtrace to each log message, plus a couple of accusatory
> elog() calls in relation_open and ExecSetupPartitionPruneState.
What do people think about adding something like this errbacktrace()
from Álvaro's patch to core PostgreSQL? If we could devise a way to
selectively enable it, it might be an easier way for users to provide
backtraces from errors.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
