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

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Дата
Msg-id 21711.1102089054@sss.pgh.pa.us
обсуждение исходный текст
Ответ на 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>)
Ответы 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>)
Список pgsql-bugs
Frank van Vugt <ftm.van.vugt@foxi.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

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Frank van Vugt
Дата:
Сообщение: Re: "invalid memory alloc request size " in deferred trigger causes transaction to fail, but the backend keeps running
Следующее
От: postgresbugs
Дата:
Сообщение: Re: Foreign keys referencing parent table fails on insert