pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Albert REINER <areiner@tph.tuwien.ac.at>
Cc: PostgreSQL-SQL <pgsql-sql@postgreSQL.org>
Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
Date: Sun, 24 Oct 1999 13:31:06 -0400
Message-ID: <3816.940786266@sss.pgh.pa.us> (raw)
In-Reply-To: <19991024171846.B27105@frithjof>

"Albert REINER" <areiner@tph.tuwien.ac.at> writes:
> I'm still using Linux kernel 2.0.35 (SuSE 5.3), but planning to
> upgrade the kernel. I also built Postgres 6.5.1 with locale support.

Hmm.  I recall several different reports of weird problems seen with
concurrently running backends that went away after an upgrade from
kernel 2.0.35 or earlier to 2.0.36 or later.  Apparently, some
significant bugs in Linux's handling of SysV semaphores were corrected
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.

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.

			regards, tom lane



view thread (8+ messages)  latest in thread

Message-ID: <3816.940786266@sss.pgh.pa.us>
Permalink:  ../3816.940786266@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/3816.940786266@sss.pgh.pa.us

 · 

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: tgl@sss.pgh.pa.us, areiner@tph.tuwien.ac.at
  Subject: Re: [SQL] Can VACUUM, but cannot do VACUUM ANALYZE
  In-Reply-To: <3816.940786266@sss.pgh.pa.us>
  References: <19991024171846.B27105@frithjof> <3816.940786266@sss.pgh.pa.us>

* 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