agora inbox for postgres@postgres.berkeley.edu  

help / color / mirror / Atom feed

To: postgres@postgres.berkeley.edu
Subject: Re: vacuum
Date: Thu, 07 May 92 16:53:06 PDT
Message-ID: <9205072358.AA08896@postgres.Berkeley.EDU> (raw)
In-Reply-To: <9205051845.AA03160@dpi.inpe.br>

you write:
> I am trying to vacuum (v3r1) a database and I am quite sure I have no other vacuum cleaner running. Why do I receive this message?
> 
> Query sent to backend is "vacuum "
> WARN:May  5 16:37:57:can't create lock file -- another vacuum cleaner running
 +?
> 
> Can someone tell me more about the vacuum cleaner?

In order to guarantee that there is only one vacuum cleaner command running
at a time the backend creates a file "pg_vlock" in the database directory.

If this file already exists the current vacuum command aborts assuming that
another vacuum is currently being run.  If a vacuum command caused a crash
it is entirely possible that the pg_vlock file was not removed.  If you are
sure there is no vacuum running you should remove the pg_vlock file by hand.


Jeff Meredith
mer@postgres.berkeley.edu

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 using the --to and --cc options:
  reply via email

  To: postgres@postgres.berkeley.edu
  Subject: Re: vacuum
  In-Reply-To: <9205072358.AA08896@postgres.Berkeley.EDU>

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

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