Re: Shared row locking - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Shared row locking
Date
Msg-id 20019.1103561261@sss.pgh.pa.us
Whole thread Raw
In response to Re: Shared row locking  ("Merlin Moncure" <merlin.moncure@rcsonline.com>)
Responses Re: Shared row locking
List pgsql-hackers
"Merlin Moncure" <merlin.moncure@rcsonline.com> writes:
> I may be over my head here, but I think lock spillover is dangerous.  In
> the extreme situations where this would happen, it would be a real
> performance buster.  Personally, I would rather see locks escalate when
> the table gets full, or at least allow this as a configuration
> parameter. 

To me, "performance buster" is better than "random, unrepeatable
deadlock failures".  In any case, if we find we *can't* implement this
in a non-performance-busting way, then it would be time enough to look
at alternatives that force the user to manage the problem for us.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Merlin Moncure"
Date:
Subject: Re: Shared row locking
Next
From: Jaime Casanova
Date:
Subject: multi-key index