Skip site navigation (1) Skip section navigation (2)

Re: Vacuum full crash

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Mikko Partio" <mpartio(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: Vacuum full crash
Date: 2008-03-30 15:40:35
Message-ID: 10439.1206891635@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-admin
"Mikko Partio" <mpartio(at)gmail(dot)com> writes:
> On Sun, Mar 30, 2008 at 12:05 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> "Mikko Partio" <mpartio(at)gmail(dot)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

In response to

Responses

pgsql-admin by date

Next:From: Bernhard D RohrerDate: 2008-03-30 16:56:22
Subject: local authentication with md5
Previous:From: Mikko PartioDate: 2008-03-30 10:56:19
Subject: Re: Vacuum full crash

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group