Re: Out of memory error causes Abort, Abort tries to allocate memory - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Out of memory error causes Abort, Abort tries to allocate memory
Date
Msg-id 5606.1161814525@sss.pgh.pa.us
Whole thread Raw
In response to Re: Out of memory error causes Abort, Abort tries to allocate memory  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: Out of memory error causes Abort, Abort tries to  (Jeff Davis <pgsql@j-davis.com>)
List pgsql-bugs
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Jeff Davis wrote:
>> * smgrGetPendingDeletes() calls palloc()
>> * palloc() fails, resulting in ERROR, causing infinite recursion

> Hmm, maybe we could have AbortTransaction switch to ErrorContext, which
> has some preallocated space, before calling RecordTransactionAbort (or
> maybe have RecordTransactionAbort itself do it).

Seems like it'd be smarter to try to free some memory before we push
forward with transaction abort.  ErrorContext has only a limited amount
of space ...

            regards, tom lane

pgsql-bugs by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Out of memory error causes Abort, Abort tries to
Next
From: "Thomas H."
Date:
Subject: Re: BUG #2712: could not fsync segment: Permission