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

Hi, all.

any idea about causes and consequences?

C:\>psql -U postgres monitor
Welcome to psql 8.2.4, the PostgreSQL interactive terminal.

Type:  \copyright for distribution terms
       \h for help with SQL commands
       \? for help with psql commands
       \g or terminate with semicolon to execute query
       \q to quit

Warning: Console code page (850) differs from Windows code page (1252)
         8-bit characters may not work correctly. See psql reference
         page "Notes for Windows users" for details.

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
server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.
!>

Att.,
Sergio

sergio nogueira <sergiopnog@gmail.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