From: | sergio nogueira <sergiopnog(at)gmail(dot)com> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | PANIC: cannot abort transaction 140578842, it was already committed |
Date: | 2009-06-23 14:57:33 |
Message-ID: | eec843740906230757t11eedf34m7d1bf6a5a58d9b35@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Ray Stell | 2009-06-23 15:01:50 | Re: Replication |
Previous Message | Jack Orenstein | 2009-06-23 14:55:53 | Re: Slight change in query leads to unexpected change in query plan |