Hello!
On 19.04.2022 18:46, Nathan Bossart wrote:
Okay, I did it this way in v5.
Recently i ran into a problem that it would be preferable in our
extended pg_stat_statements to use MaxBackEnds in _PG_Init() but it's
equal to zero here.
And i was very happy to find this patch and this thread. It was not
only very interesting and informative for me but also solves the current
problem. Patch is applied cleanly on current master. Tests under Linux
and Windows were successful.
I've tried this patch with our extended pg_stat_statements and checked
that MaxBackends has the correct value during extra shmem allocating.
Thanks a lot!
+1 for this patch.
I have a little doubt about the comment in postmaster.c: "Now that
loadable modules have had their chance to alter any GUCs". Perhaps this
comment is too general. Not sure that it is possible to change any
arbitrary GUC here.
And maybe not bad to add Assert(size > 0) in RequestAddinShmemSpace() to
see that the size calculation in contrib was wrong.
With best regards,
--
Anton A. Melnikov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
