Re: [HACKERS] Why do we need pg_vlock? - Mailing list pgsql-hackers

From Vadim Mikheev
Subject Re: [HACKERS] Why do we need pg_vlock?
Date
Msg-id 37E58D1B.F7196D10@krs.ru
Whole thread Raw
In response to Re: [HACKERS] Why do we need pg_vlock?  (Bruce Momjian <maillist@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian wrote:
> 
> > It seems to me there's no fundamental reason why there couldn't be
> > two VACUUMs running concurrently in a database.  With the locking
> > we are doing now, it should be safe enough.  So, I'd like to propose
> > that we get rid of the pg_vlock lock file.  It doesn't have any useful
> > purpose but it does force manual intervention by the dbadmin to recover
> > if a VACUUM crashes :-(
> >
> > Comments?  Did I miss something about why we can't have more than one
> > vacuum process?
> 
> I vote for removal.  Lock files are hacks, usually.

Agreed.

Vadim


pgsql-hackers by date:

Previous
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] Notice: heap_open/close changes committed
Next
From: Vadim Mikheev
Date:
Subject: Re: [HACKERS] Anyone understand shared buffer refcount mechanism?