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 10560.1102035571@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  (Frank van Vugt <ftm.van.vugt@foxi.nl>)
List pgsql-bugs
Tree view 
Frank van Vugt <ftm.van.vugt@foxi.nl> writes:
>> What I'd be inclined
>> to try is tracing through the transaction to see where
>> SerializableSnapshotData.xcnt or LatestSnapshotData.xcnt gets clobbered
>> from.  It'd be mighty tedious if you have to fall back on a software
>> watchpoint though.

> A hint on the expression(s) to use would be appreciated !

(gdb) watch SerializableSnapshotData.xcnt
Hardware watchpoint 1: SerializableSnapshotData.xcnt
(gdb) watch LatestSnapshotData.xcnt
Hardware watchpoint 2: LatestSnapshotData.xcnt
(gdb) cont
Continuing.

The only "authorized" place to set these is the assignment near the
bottom of GetSnapshotData(), which would normally get hit about
once per command.

            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: Tom Lane
Date:
Subject: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running