Re: LWLocks by LockManager slowing large DB

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Paul Friedman <paul(dot)friedman(at)streetlightdata(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: LWLocks by LockManager slowing large DB
Date: 2021-04-13 22:29:08
Message-ID: 3395561.1618352948@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2021-04-13 11:47:06 -0700, Paul Friedman wrote:
>> YES!!! This completely alleviates the bottleneck and I'm able to run the
>> queries full-throttle. Thank you SO much for your help+insight.

> Cool. And damn: I can't immediately think of a way to optimize this to
> not require this kind of hack in the future.

Maybe the same thing we do with user tables, ie not give up the lock
when we close a toast rel? As long as the internal lock counters
are 64-bit, we'd not have to worry about overflowing them.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Paul Friedman 2021-04-13 22:45:12 RE: LWLocks by LockManager slowing large DB
Previous Message Alvaro Herrera 2021-04-13 20:54:59 Re: LWLocks by LockManager slowing large DB