Re: PANIC: cannot abort transaction 140578842, it was already committed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: sergio nogueira <sergiopnog(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: PANIC: cannot abort transaction 140578842, it was already committed
Date: 2009-06-23 15:47:10
Message-ID: 18244.1245772030@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

sergio nogueira <sergiopnog(at)gmail(dot)com> writes:
> monitor=# vacuum full
> monitor-# ;
> ERROR: could not truncate relation 18293/18295/19113 to 68908 blocks:
> Permission denied
> PANIC: cannot abort transaction 140578842, it was already committed

The PANIC is a known problem if vacuum full fails at the wrong place.
The real issue here is why are you getting permission denied on the
truncate? Since this is apparently a Windows installation, I'm betting
on interference from some broken Windows antivirus software.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message DaNieL..! 2009-06-23 15:55:36 Re: Please suggest me on my table design (indexes!)
Previous Message justin 2009-06-23 15:37:32 Re: Please suggest me on my table design (indexes!)