Received: from frithjof.reiner (qmailr@c35.dialin.tuwien.ac.at [192.35.243.45]) by hub.org (8.9.3/8.9.3) with SMTP id DAA99673 for ; Sat, 23 Oct 1999 03:21:05 -0400 (EDT) (envelope-from areiner@tph.tuwien.ac.at) Received: (qmail 1068 invoked by uid 500); 23 Oct 1999 07:18:19 -0000 From: "Albert REINER" Date: Sat, 23 Oct 1999 09:18:19 +0200 To: PostgreSQL-SQL Subject: Can VACUUM, but cannot do VACUUM ANALYZE Message-ID: <19991023091819.C833@frithjof> Mail-Followup-To: PostgreSQL-SQL Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i Hi! Every couple of days I run "vacuum analyze" on every db on my system (from a shell script). Now there is one small database (two tables, one SQL-function) where I get the following (in psql): > albert@frithjof:/home/albert > psql > Welcome to the POSTGRESQL interactive sql monitor: > Please read the file COPYRIGHT for copyright terms of POSTGRESQL > [PostgreSQL 6.5.1 on i586-pc-linux-gnulibc1, compiled by gcc 2.7.2.1] > > type \? for help on slash commands > type \q to quit > type \g or terminate with semicolon to execute query > You are currently connected to the database: albert > > albert=> vacuum; > VACUUM > albert=> vacuum analyze; > NOTICE: AbortTransaction and not in in-progress state > pqReadData() -- backend closed the channel unexpectedly. > This probably means the backend terminated abnormally > before or while processing the request. > We have lost the connection to the backend, so further processing is impossible. Terminating. > I.e., I can VACUUM, but I cannot do VACUUM ANALYZE. Why should analyze do an ABORT? By the way, I do not notice any strange behavior with this database, and pg_dump works fine on it. Any ideas what might be at fault and how to fix this? Thanks in advance, Albert. -- -------------------------------------------------------------------------- Albert Reiner Deutsch * English * Esperanto * Latine --------------------------------------------------------------------------