| From: | "wangsh(dot)fnst(at)fujitsu(dot)com" <wangsh(dot)fnst(at)fujitsu(dot)com> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | RE: make MaxBackends available in _PG_init |
| Date: | 2021-08-03 00:19:42 |
| Message-ID: | OSBPR01MB42141AC4A17F27EE7C2F301EF2F09@OSBPR01MB4214.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Bossart, Nathan <bossartn(at)amazon(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2021-08-03 00:27:38 | Re: Record a Bitmapset of non-pruned partitions |
| Previous Message | Bossart, Nathan | 2021-08-02 23:28:19 | Re: archive status ".ready" files may be created too early |