"Mikko Partio" <mpartio@xxxxxxxxx> writes: > On Sun, Mar 30, 2008 at 12:05 AM, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: >> "Mikko Partio" <mpartio@xxxxxxxxx> 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 -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
