Re: Revised Patch to allow multiple table locks in "Unison"

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Fernando Nasser <fnasser(at)cygnus(dot)com>, Neil Padgett <npadgett(at)redhat(dot)com>, "pgsql-patches(at)postgresql(dot)org" <pgsql-patches(at)postgresql(dot)org>
Subject: Re: Revised Patch to allow multiple table locks in "Unison"
Date: 2001-08-02 21:32:20
Message-ID: 200108022132.f72LWKL22888@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> Fernando Nasser <fnasser(at)cygnus(dot)com> writes:
> > What about having the syntax
> > LOCK a,b,c;
> > now just as a shorthand for
> > LOCK a;
> > LOCK b;
> > LOCK c;
> > This would save typing and allow for Oracle compatibility.
>
> This seems fine to me (and in fact I thought we'd already agreed to it).
> Maybe some day we will get ambitious enough to make it do
> parallel-locking, but for now we can get 80% of what we want with 0.8%
> of the effort ;-)

I think that was my point, that even in the lock manager, we would have
starvation problems and things would get very complicated. In
hindsight, the idea of locking multiple tables in unison was just not
reasonable in PostgreSQL at this time.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Myers 2001-08-02 21:54:28 Re: OID wraparound: summary and proposal
Previous Message Hannu Krosing 2001-08-02 21:25:51 Re: Re: OID wraparound: summary and proposal

Browse pgsql-patches by date

  From Date Subject
Next Message Dave Page 2001-08-02 21:54:19 RE: Patch for Improved Syntax Error Reporting
Previous Message Tom Lane 2001-08-02 21:16:11 Re: Patch for Improved Syntax Error Reporting