Re: Good name for new lock type for VACUUM?

From: Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Good name for new lock type for VACUUM?
Date: 2001-06-25 01:42:40
Message-ID: 3B369710.894DA7A2@tpf.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>
> Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> Still, it's an interesting alternative. Comments anyone?
>
> > SelfExclusiveLock is clear and can't be confused with other lock types.
>
> It could possibly be made a little less dangerous if "SelfExclusiveLock"
> were defined to conflict with itself and AccessExclusiveLock (and
> nothing else). That would at least mean that holding SelfExclusiveLock
> would guarantee the table not go away under you; so there might be
> scenarios where holding just that lock would make sense.
>
> Still, I'm not sure that this lock type is as flexible as it seems at
> first glance.

I don't think "SelfExclusiveLock" is an excellent lock either.
However it seems to point out the reason why we couldn't
place(name) "VacuumLock" properly in our locking system.

regards,
Hiroshi Inoue

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Toback 2001-06-25 05:16:47 Re: Instrumenting and Logging in JDBC
Previous Message Tatsuo Ishii 2001-06-25 01:03:05 Re: stuck spin lock with many concurrent users