| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | 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-02 22:58:49 |
| Message-ID: | 23DC344C-97D9-413E-8911-3516BB151BB5@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/2/21, 3:42 PM, "Andres Freund" <andres(at)anarazel(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Rowley | 2021-08-02 22:59:25 | Re: Use generation context to speed up tuplesorts |
| Previous Message | Andres Freund | 2021-08-02 22:42:04 | Re: make MaxBackends available in _PG_init |