Re: Postgres is not able to handle more than 4k tables!? - Mailing list pgsql-hackers

From Grigory Smolkin
Subject Re: Postgres is not able to handle more than 4k tables!?
Date
Msg-id 1ab992dc-48b2-8bb9-239e-264148863f7e@postgrespro.ru
Whole thread Raw
In response to Postgres is not able to handle more than 4k tables!?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
Responses Re: Postgres is not able to handle more than 4k tables!?  (Konstantin Knizhnik <k.knizhnik@postgrespro.ru>)
List pgsql-hackers
On 7/8/20 11:41 PM, Konstantin Knizhnik wrote:
>
> So looks like NUM_LOCK_PARTITIONS and MAXNUMMESSAGES  constants have 
> to be replaced with GUCs.
> To avoid division, we can specify log2 of this values, so shift can be 
> used instead.
> And MAX_SIMUL_LWLOCKS should be defined as NUM_LOCK_PARTITIONS + 
> NUM_INDIVIDUAL_LWLOCKS + NAMED_LWLOCK_RESERVE.
>
Because I was involved in this particular case and don`t want it to 
became a habit, I`m volunteering to test whatever patch this discussion 
will produce.

-- 
Grigory Smolkin
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company




pgsql-hackers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: Postgres is not able to handle more than 4k tables!?
Next
From: Tom Lane
Date:
Subject: Re: Is this a bug in pg_current_logfile() on Windows?