pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Albert REINER <areiner@tph.tuwien.ac.at>
To: PostgreSQL-SQL <pgsql-sql@postgreSQL.org>
Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
Date: Mon, 25 Oct 1999 17:09:59 +0200
Message-ID: <19991025170959.B552@frithjof> (raw)
In-Reply-To: <3816.940786266@sss.pgh.pa.us>
References: <19991024171846.B27105@frithjof>
	<3816.940786266@sss.pgh.pa.us>

On Sun, Oct 24, 1999 at 01:31:06PM -0400, Tom Lane wrote:
> "Albert REINER" <areiner@tph.tuwien.ac.at> 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                                   <areiner@tph.tuwien.ac.at>
Deutsch       *       English       *       Esperanto       *       Latine
--------------------------------------------------------------------------



view thread (8+ messages)

Message-ID: <19991025170959.B552@frithjof>
Permalink:  ../19991025170959.B552@frithjof/
Also on:    postgresql.org/message-id/19991025170959.B552@frithjof

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: areiner@tph.tuwien.ac.at
  Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
  In-Reply-To: <19991025170959.B552@frithjof>
  References: <19991024171846.B27105@frithjof> <3816.940786266@sss.pgh.pa.us> <19991025170959.B552@frithjof>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox