Re: make MaxBackends available in _PG_init - Mailing list pgsql-hackers

From Bossart, Nathan
Subject Re: make MaxBackends available in _PG_init
Date
Msg-id 7FDD160A-4E31-45CE-8B6F-8FE508E324F7@amazon.com
Whole thread Raw
In response to Re: make MaxBackends available in _PG_init  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
On 1/7/22, 10:12 AM, "Bossart, Nathan" <bossartn@amazon.com> wrote:
> While that approach would provide a way to safely retrieve the value,
> I think it would do little to prevent the issue in practice.  If the
> size of the patch is a concern, we could also convert MaxBackends into
> a macro for calling GetMaxBackends().  This could also be a nice way
> to avoid breaking extensions that are using it correctly while
> triggering ERRORs for extensions that are using it incorrectly.  I've
> attached a new version of the patch that does it this way.

v5 didn't work with EXEC_BACKEND.  Here is a new revision.

Nathan


Attachment

pgsql-hackers by date:

Previous
From: Jeff Davis
Date:
Subject: Re: Disallow quorum uncommitted (with synchronous standbys) txns in logical replication subscribers
Next
From: "Bossart, Nathan"
Date:
Subject: Re: Worth using personality(ADDR_NO_RANDOMIZE) for EXEC_BACKEND on linux?