Postgres Pro
Downloads
Home   >   mailing lists

Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running - Mailing list pgsql-bugs

From Frank van Vugt
Subject Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Date
Msg-id 200412030226.50102.ftm.van.vugt@foxi.nl
Whole thread Raw
In response to Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Tree view 
> 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.

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Next
From: Tom Lane
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running