From: Tom Lane <tgl@sss.pgh.pa.us>
To: Mikko Partio <mpartio@gmail.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Vacuum full crash
Date: Sun, 30 Mar 2008 11:40:35 -0400
Message-ID: <10439.1206891635@sss.pgh.pa.us> (raw)
In-Reply-To: <2ca799770803300356r185b1adbv2ab17c7cc8f212a7@mail.gmail.com>
References: <2ca799770803291340p75d8a4e2o7dfd6c61e73270f6@mail.gmail.com>
<21772.1206824718@sss.pgh.pa.us>
<2ca799770803300356r185b1adbv2ab17c7cc8f212a7@mail.gmail.com>
"Mikko Partio" <mpartio@gmail.com> writes:
> On Sun, Mar 30, 2008 at 12:05 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> "Mikko Partio" <mpartio@gmail.com> writes:
>>> 2008-03-29 22:25:15 EET [26841]: [3-1] PANIC: cannot abort transaction
>>> 3778747509, it was already committed
>>
>> Yeah, this is a well-known problem with VACUUM FULL ...
> Ok, that's good to know. Is there a bugfix on the way or is it more like a
> 'feature'?
It would be good to fix it I suppose, but what with VACUUM FULL being on
the edge of deprecation anyway, it's hard to muster enthusiasm for doing
a (probably) large additional amount of work on it, I think most
hackers would prefer to spend time on making it unnecessary than making
it more bulletproof.
Note that there is (AFAIK) no risk of loss of committed data from this
bug. The fact that the PANIC kills all your other sessions is annoying,
but in the scenarios where this is likely to happen you're trying to
stop them all anyway ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, mpartio@gmail.com
Subject: Re: Vacuum full crash
In-Reply-To: <10439.1206891635@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox