| From: | Konstantin Knizhnik <k(dot)knizhnik(at)postgrespro(dot)ru> |
|---|---|
| To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Postgres is not able to handle more than 4k tables!? |
| Date: | 2020-07-10 07:18:36 |
| Message-ID: | 2f6cded7-907b-1b6a-3457-cfcc58bcb3a4@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| skip_autovacuum.patch | text/x-patch | 5.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2020-07-10 07:24:25 | Re: Postgres is not able to handle more than 4k tables!? |
| Previous Message | Andrey M. Borodin | 2020-07-10 06:55:47 | Re: Yet another fast GiST build (typo) |