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 Tom Lane
Subject Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Date
Msg-id 10809.1102036915@sss.pgh.pa.us
Whole thread Raw
In response to Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
Responses Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
List pgsql-bugs
Tree view 
Frank van Vugt <ftm.van.vugt@foxi.nl> writes:
>>>> Does anything happen before the SAVEPOINT?
>
>>>> Actually, the SQL involved is v7.4.6,
>>
>> Not with that backtrace, it isn't.

> Excuse me?

> I'm running v8.0.0beta5,

Oh, I thought you meant the backend was 7.4.6.

> but the sql-statements that are in my source-tree are
> all still 'based on v7.4.6', i.e. there is no occurence of the word
> 'savepoint' in the whole tree.

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 ...

            regards, tom lane

pgsql-bugs by date:

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