Received: from frithjof.reiner (qmailr@c68.dialin.tuwien.ac.at [192.35.243.78]) by hub.org (8.9.3/8.9.3) with SMTP id PAA87024 for ; Sun, 24 Oct 1999 15:06:16 -0400 (EDT) (envelope-from areiner@tph.tuwien.ac.at) Received: (qmail 27538 invoked by uid 500); 24 Oct 1999 15:48:30 -0000 From: "Albert REINER" Date: Sun, 24 Oct 1999 17:48:30 +0200 To: PostgreSQL-SQL Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE Message-ID: <19991024174830.A27504@frithjof> Mail-Followup-To: PostgreSQL-SQL Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Sorry, should have gone to the list in the first place: On Sat, Oct 23, 1999 at 12:18:33PM -0400, Tom Lane wrote: > "Albert REINER" writes: > >> albert=> vacuum analyze; > >> NOTICE: AbortTransaction and not in in-progress state > >> pqReadData() -- backend closed the channel unexpectedly. > ... > to back-patch into 6.5.*. In the meantime, the only way to find out > what that original error message was is to consult the postmaster log (or running strace psql) > file --- you are running the postmaster with stdout/stderr going to > some logfile, I hope. It should show up right before the NOTICE and > then the postmaster's response to the backend coredump. ... ERROR: vacuum: can't destroy lock file! NOTICE: AbortTransaction and not in in-progress state ... But where can I find this lock file, and can I simply remove it? > Once we have vacuum's error message we can maybe offer some useful > counsel. Looking forward to that, Albert. -- -------------------------------------------------------------------------- Albert Reiner Deutsch * English * Esperanto * Latine -------------------------------------------------------------------------- ----- End forwarded message ----- -- -------------------------------------------------------------------------- Albert Reiner Deutsch * English * Esperanto * Latine --------------------------------------------------------------------------