Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running

From: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running
Date: 2004-12-03 01:26:50
Message-ID: 200412030226.50102.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> Hmm. The line number referenced for CommitTransactionCommand() is
> definitely in code that is only entered after a savepoint, but I see
> it is an identical code path to some other arms of the switch()
> command. Probably the compiler decided to merge those arms. You might
> want to back off the compiler optimization level a step so you can get
> more readable tracebacks ...

Yup, will do that as well.

Will read any comments you may have on the TRAP backtrace in a couple of
hours, need to take myself offline for a while ;)

--
Best,

Frank.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2004-12-03 01:35:53 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running
Previous Message Tom Lane 2004-12-03 01:21:55 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running