Hi, On 2015-08-29 11:06:05 -0500, Jim Nasby wrote: > Stack trace below. Relevant assert:
What exact revision is this on? Either there's some aggressive inlining going on, or these lines don't entirely match up with HEAD. That's compiled with optimization, isn't it? Could you compile with -O0? Can you go up to > > frame #19: 0x0000000116295f1f > > plpgsql.so`exec_stmt_block(estate=0x00007fff532c0090, > > block=0x00007fa3f53a21d0) + 2095 at pl_exec.c:1300 and do 'disass/m' to see where we actually are? The area around #19 likely is the PG_CATCH inside exec_stmt_block. So what's happening is that there's an exception raised, while handling the previous exception. And apparently we're not doing that entirely right. Besides the line numbers "during exception cleanup" hints at that. Greetings, Andres Freund -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
