Re: How to solve "too many Lwlocks taken"? - Mailing list pgsql-hackers

From Andres Freund
Subject Re: How to solve "too many Lwlocks taken"?
Date
Msg-id 20230207181742.6qaimfgu4cprtndm@awork3.anarazel.de
Whole thread Raw
In response to How to solve "too many Lwlocks taken"?  ("jacktby@gmail.com" <jacktby@gmail.com>)
List pgsql-hackers
Hi,

On 2023-02-07 22:16:36 +0800, jacktby@gmail.com wrote:
> 
> I'm trying to write am table_am extension. But I get "too many Lwlocks taken" after I insert 
> too many tuples. So I try to use UnLockBuffers() everywhere; but it still give me "too many Lwlocks taken",
> So how should I release All locks?

This indicates that you aren't actually releasing all the lwlocks. You can
inspect
static int    num_held_lwlocks = 0;
static LWLockHandle held_lwlocks[MAX_SIMUL_LWLOCKS];
in a debugger to see which locks you didn't release.


You're currently starting multiple threads with questions a week. Could you at
least keep them in one thread?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Jacob Champion
Date:
Subject: Re: Can we let extensions change their dumped catalog schemas?
Next
From: Andres Freund
Date:
Subject: Re: [PATCH] Make ON CONFLICT DO NOTHING and ON CONFLICT DO UPDATE consistent