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

From Konstantin Knizhnik
Subject Re: Postgres is not able to handle more than 4k tables!?
Date
Msg-id 2f6cded7-907b-1b6a-3457-cfcc58bcb3a4@postgrespro.ru
Whole thread Raw
In response to Re: Postgres is not able to handle more than 4k tables!?  (Grigory Smolkin <g.smolkin@postgrespro.ru>)
Responses Re: Postgres is not able to handle more than 4k tables!?
List pgsql-hackers

On 09.07.2020 22:16, Grigory Smolkin wrote:
>
> 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.
>
You are welcome:)


Attachment

pgsql-hackers by date:

Previous
From: "Andrey M. Borodin"
Date:
Subject: Re: Yet another fast GiST build (typo)
Next
From: Laurenz Albe
Date:
Subject: Re: Postgres is not able to handle more than 4k tables!?