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:11:59
Message-ID: 200412030211.59880.ftm.van.vugt@foxi.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> > A hint on the expression(s) to use would be appreciated !
> (gdb) watch SerializableSnapshotData.xcnt

I could have thought of that ;)

(I misinterpreted what you meant by SerializableSnapshotData.xcnt, wouldn't
have asked otherwise)

Anyway, I just confirmed that hardware watchpoints are available, so I'll
follow this up first thing in the morning.

--
Best,

Frank.

In response to

Browse pgsql-bugs by date

  From Date Subject
Next 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
Previous Message Frank van Vugt 2004-12-03 01:10:09 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running