Re: Postgres is not able to handle more than 4k tables!?

From: Grigory Smolkin <g(dot)smolkin(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-09 19:16:37
Message-ID: 1ab992dc-48b2-8bb9-239e-264148863f7e@postgrespro.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

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