Jeff Davis wrote: > I found the root cause of the bug I reported at: > > http://archives.postgresql.org/pgsql-bugs/2006-10/msg00211.php > > What happens is this: > * Out of memory condition causes an ERROR > * ERROR triggers an AbortTransaction() > * AbortTransaction() calls RecordTransactionAbort() > * RecordTransactionAbort calls smgrGetPendingDeletes() > * smgrGetPendingDeletes() calls palloc() > * palloc() fails, resulting in ERROR, causing infinite recursion > * elog.c detects infinite recursion, and elevates it to PANIC > > I'm not sure how easy this is to fix, but I asked on IRC and got some > agreement that this is a bug.
Hmm, maybe we could have AbortTransaction switch to ErrorContext, which has some preallocated space, before calling RecordTransactionAbort (or maybe have RecordTransactionAbort itself do it). Problem is, what happens if ErrorContext is filled up by doing this? At that point we will be severely fscked up, and you probably won't get the PANIC either. (Maybe it doesn't happen in this particular case, but seems a real risk.) -- Alvaro Herrera http://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
