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

From wangsh.fnst@fujitsu.com
Subject RE: make MaxBackends available in _PG_init
Date
Msg-id OSBPR01MB42141AC4A17F27EE7C2F301EF2F09@OSBPR01MB4214.jpnprd01.prod.outlook.com
Whole thread Raw
In response to Re: make MaxBackends available in _PG_init  ("Bossart, Nathan" <bossartn@amazon.com>)
List pgsql-hackers
Hi,

Bossart, Nathan <bossartn@amazon.com> wrote:

> I just encountered the same thing, so I am bumping this thread.
Thank you for bumping this thread.

> > 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. 

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

I think this is a good idea.

Shenhao Wang
Best regards

pgsql-hackers by date:

Previous
From: "Bossart, Nathan"
Date:
Subject: Re: archive status ".ready" files may be created too early
Next
From: David Rowley
Date:
Subject: Re: Record a Bitmapset of non-pruned partitions