Horton

Re: Complier warnings on mingw gcc 4.5.0

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Itagaki Takahiro <itagaki.takahiro@gmail.com>, Hiroshi Inoue <inoue@tpf.co.jp>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Date: 2010-12-15T05:08:24Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Make the win32 putenv() override update *all* present versions of the

  2. Remove the use of the pg_auth flat file for client authentication.


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