Thomas Munro <thomas.munro@xxxxxxxxx> writes: > A fast way to find out would be to get one of these people who can > reproduce the problem to recompile PostgreSQL with that error changed > to a PANIC, and examine the resulting smoldering core. (Someone had a > proposal to make PostgreSQL errors optionally dump the function call > stack with backtrace(3) even in regular production builds, which would > make this kind of investigations go faster, I wonder what happened to > that.) Can't speak for other people, but I remember experimenting with glibc's backtrace(3) and being so underwhelmed by the usefulness of the information presented that I thought incorporating it would be mostly a waste of effort. Maybe there's an argument that it's better than nothing at all; but I think we'd still be driven to asking people to get stack traces with better tools. regards, tom lane
