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 23DC344C-97D9-413E-8911-3516BB151BB5@amazon.com
Whole thread Raw
In response to Re: make MaxBackends available in _PG_init  (Andres Freund <andres@anarazel.de>)
Responses RE: make MaxBackends available in _PG_init
List pgsql-hackers
On 8/2/21, 3:42 PM, "Andres Freund" <andres@anarazel.de> wrote:
> I've wondered, independent of this thread, about not making MaxBackends
> externally visible, and requiring a function call to access it. It should be
> easier to find cases of misuse if we errored out when accessed at the wrong
> time. And we could use that opportunity to add flags that determine which
> types of backends are included (e.g. not including autovac, or additionally
> including aux workers or prepared xacts).

I'm not opposed to this.  I can work on putting a patch together if no
opposition materializes.

Nathan


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: make MaxBackends available in _PG_init
Next
From: David Rowley
Date:
Subject: Re: Use generation context to speed up tuplesorts