On 06/15/2011 05:52 PM, BangarRaju Vadapalli wrote:
> 7. Attached the database side and application side logs.
Yeah, there's definitely a crash, you just chopped it off in the
abbreviated logs you sent earlier. With this kind of log volume that's
easy enough to do.
Anyway, the crash is:
2011-06-15 13:55:59 IST postgres epimart PANIC: XX000: cannot abort
transaction 19773146, it was already committed
from:
2011-06-15 13:55:59 IST postgres epimart ERROR: XX000: could not open
relation base/2850136/3344343_vm: A blocking operation was interrupted
by a call to WSACancelBlockingCall.^M
2011-06-15 13:55:59 IST postgres epimart LOCATION: mdopen,
.\src\backend\storage\smgr\md.c:526
2011-06-15 13:55:59 IST postgres epimart STATEMENT: COMMIT
2011-06-15 13:55:59 IST postgres epimeta DEBUG: 00000: CommitTransaction
2011-06-15 13:55:59 IST postgres epimeta LOCATION:
ShowTransactionState, .\src\backend\access\transam\xact.c:4074
2011-06-15 13:55:59 IST postgres epimart WARNING: 01000:
AbortTransaction while in COMMIT state
2011-06-15 13:55:59 IST postgres epimart LOCATION: AbortTransaction,
.\src\backend\access\transam\xact.c:2011
2011-06-15 13:55:59 IST postgres epimart DEBUG: 00000: StartTransaction
2011-06-15 13:55:59 IST postgres epimart LOCATION:
ShowTransactionState, .\src\backend\access\transam\xact.c:4074
2011-06-15 13:55:59 IST postgres epimart PANIC: XX000: cannot abort
transaction 19773146, it was already committed
2011-06-15 13:55:59 IST postgres epimart LOCATION:
RecordTransactionAbort, .\src\backend\access\transam\xact.c:1200
While I recall some known issues that resulted in panics because of
"cannot abort transaction" errors, I seem to recall that they were
related to autovacuum, which this doesn't particularly seem to be.
I'd still recommend updating to 8.4.8, as 8.4.2 was patched six more
times for good reasons.
--
Craig Ringer