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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl>
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 15:50:54
Message-ID: 21711.1102089054@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Frank van Vugt <ftm(dot)van(dot)vugt(at)foxi(dot)nl> writes:
>> This is the expected case. The failure in CopySnapshot has got to
>> indicate that somebody set one or the other field to some bizarrely
>> large value, though. I take it you didn't run the watchpointed backend
>> far enough to get the memory-alloc error?

> Oh, but I did.....

[ scratches head ... ] AFAICS, the CopySnapshot that gets the error
must be trying to copy one or the other of those snapshots. Maybe you
should look at the address passed to CopySnapshot and see what it's
really pointing at, and where it came from.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message postgresbugs 2004-12-03 18:12:24 Re: Foreign keys referencing parent table fails on insert
Previous Message Frank van Vugt 2004-12-03 15:26:08 Re: "invalid memory alloc request size <n>" in deferred trigger causes transaction to fail, but the backend keeps running