Re: Revised Patch to allow multiple table locks in "Unison" - Mailing list pgsql-patches

From Bruce Momjian
Subject Re: Revised Patch to allow multiple table locks in "Unison"
Date
Msg-id 200107301620.f6UGKwq07511@candle.pha.pa.us
Whole thread Raw
In response to Re: Revised Patch to allow multiple table locks in "Unison"  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Revised Patch to allow multiple table locks in "Unison"  (Neil Padgett <npadgett@redhat.com>)
List pgsql-patches
> Bruce Momjian <pgman@candle.pha.pa.us> writes:
> > Actually, with this new code, we could go back to locking in oid order,
> > which would eliminate the problem.
>
> No it wouldn't.  If anything, locking in a *randomized* order would be
> the best bet.  But I have no confidence in this approach, anyway.

I am looking for a way to get this in there without munging the lock
code, which is already quite complex.  What about doing some sort of
small sleep after we reset back to the beginning of the table list.

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

pgsql-patches by date:

Previous
From: Fernando Nasser
Date:
Subject: Re: Revised Patch to allow multiple table locks in "Unison"
Next
From: Bruce Momjian
Date:
Subject: Re: Revised Patch to allow multiple table locks in "Unison"