From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Out of memory error causes Abort, Abort tries to allocate memory |
Date: | 2006-10-25 22:15:25 |
Message-ID: | 5606.1161814525@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Alvaro Herrera <alvherre(at)commandprompt(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas H. | 2006-10-25 23:53:41 | Re: BUG #2712: could not fsync segment: Permission |
Previous Message | Jeff Davis | 2006-10-25 21:03:42 | Re: Out of memory error causes Abort, Abort tries to |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2006-10-25 22:43:58 | Traveling for two weeks |
Previous Message | Tom Lane | 2006-10-25 22:12:10 | Re: Bug in 8.2B1 plpgsql ... |