| From: | The Hermit Hacker <scrappy(at)hub(dot)org> |
|---|---|
| To: | Michael Yeung <michaely(at)alphanet(dot)net(dot)au> |
| Cc: | "'Postgres'" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] Unlock the vacuum |
| Date: | 1998-04-30 03:40:28 |
| Message-ID: | Pine.BSF.3.96.980430003957.466L-100000@thelab.hub.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 30 Apr 1998, Michael Yeung wrote:
> Dear all,
>
> Can anyone tell me how to unlocak a vacuum ? Because last time i run the vacuum and stop while running. When i do a vacuum again this morning, it says
>
> michaely=> vacuum;
> WARN: Can't create a lock file - another vacuum cleaner running ?
Assuming that you are *sure* there are no other vacuum processes
running, look for:
<PGHOME>/data/base/<database>/pg_vlock
And remove that...
Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy(at)hub(dot)org secondary: scrappy(at){freebsd|postgresql}.org
| From | Date | Subject | |
|---|---|---|---|
| Next Message | ocie | 1998-04-30 03:51:58 | Re: [HACKERS] Re: [PATCHES] S_LOCK reduced contention through backoff patch |
| Previous Message | Brett McCormick | 1998-04-30 03:09:05 | text patch -- sugg cmd when run as root |