Received: from frithjof.reiner (qmailr@c26.dialin.tuwien.ac.at [192.35.243.36]) by hub.org (8.9.3/8.9.3) with SMTP id MAA13905 for ; Mon, 25 Oct 1999 12:33:39 -0400 (EDT) (envelope-from areiner@tph.tuwien.ac.at) Received: (qmail 568 invoked by uid 500); 25 Oct 1999 15:09:59 -0000 From: "Albert REINER" Date: Mon, 25 Oct 1999 17:09:59 +0200 To: PostgreSQL-SQL Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE Message-ID: <19991025170959.B552@frithjof> Mail-Followup-To: PostgreSQL-SQL References: <19991024171846.B27105@frithjof> <3816.940786266@sss.pgh.pa.us> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.6i In-Reply-To: <3816.940786266@sss.pgh.pa.us>; from Tom Lane on Sun, Oct 24, 1999 at 01:31:06PM -0400 On Sun, Oct 24, 1999 at 01:31:06PM -0400, Tom Lane wrote: > "Albert REINER" writes: ... > at 2.0.36 --- and Postgres depends heavily on semaphores. However, > I wouldn't really expect that to be a problem unless you were running > several backends concurrently. It wasn't clear if you had other > things going on besides the VACUUM or not. No, just the vacuum. > I forgot to mention yesterday: if you track down the vacuum error > message as I suggested, and it's something about "can't destroy > lock file", then you just need to update to 6.5.2 and the problem > should go away. If it's something else then more investigation > will be needed. Thank you for this help. I'll try as soon as possible. By the way, is this problem likely to affect data integrity or the basic functioning of the database? As far as I understand, the vacuum-analyze failure only means that some queries are slower than necessary, or not? Bye, Albert. -- -------------------------------------------------------------------------- Albert Reiner Deutsch * English * Esperanto * Latine --------------------------------------------------------------------------