Re: [HACKERS] NOTICE: AbortTransaction and not in in-progress

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kristofer Munn <kmunn(at)munn(dot)com>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] NOTICE: AbortTransaction and not in in-progress
Date: 1999-12-01 23:26:53
Message-ID: 26153.944090813@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kristofer Munn <kmunn(at)munn(dot)com> writes:
> And in the system log I see:
> FATAL 1: transaction commit failed on magnetic disk
> NOTICE: AbortTransaction and not in in-progress

Ugh. As near as I can tell, the "transaction commit failed" message
can only come out if fsync() returns a failure indication. And that
basically shouldn't be happening, unless you've got flaky disk hardware.

> Any suggestions?

I'll bet it stops happening if you run with -o -F (no fsync) ;-).
But as for non-band-aid solutions, I haven't a clue. Anyone?

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Hiroshi Inoue 1999-12-02 00:56:19 RE: [HACKERS] Re: [GENERAL] drop/rename table and transactions
Previous Message Kristofer Munn 1999-12-01 21:24:23 NOTICE: AbortTransaction and not in in-progress