On 12/14/2010 12:42 PM, Tom Lane wrote:
> Another line of attack is that we know from the response packet that the
> failure is being reported at guc.c:4794. It would be really useful to
> know what the call stack is there. Could you change that elog to an
> elog(PANIC) and get a stack trace from the ensuing core dump?
>
That didn't work. But git bisect says it's this commit that's to blame:
<https://github.com/postgres/postgres/commit/e710b65c1c56ca7b91f662c63d37ff2e72862a94>
It's too late to dig further now.
cheers
andrew