Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Out of memory error causes Abort, Abort tries to allocate memory
- 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: Wed, 25 Oct 2006 18:15:25 -0400
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
- Follow-Ups:
- Re: Out of memory error causes Abort, Abort tries to
- From: Jeff Davis
- Re: Out of memory error causes Abort, Abort tries to
- References:
- Out of memory error causes Abort, Abort tries to allocate memory
- From: Jeff Davis
- Re: Out of memory error causes Abort, Abort tries to allocate memory
- From: Alvaro Herrera
- Out of memory error causes Abort, Abort tries to allocate memory
- Prev by Date: Re: Out of memory error causes Abort, Abort tries to
- Next by Date: Re: BUG #2712: could not fsync segment: Permission
- Previous by thread: Re: Out of memory error causes Abort, Abort tries to
- Next by thread: Re: Out of memory error causes Abort, Abort tries to
- Indexes: