| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | 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 23:13:26 |
| Message-ID: | 34ACE850-D6F5-4E3E-8835-DD48264964E4@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/2/21, 4:02 PM, "Bossart, Nathan" <bossartn(at)amazon(dot)com> wrote:
> 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.
Here is a first attempt.
Nathan
| Attachment | Content-Type | Size |
|---|---|---|
| v1-0001-Disallow-external-access-to-MaxBackends.patch | application/octet-stream | 30.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2021-08-03 23:18:31 | Re: Release 13 of the PostgreSQL BuildFarm client |
| Previous Message | Bossart, Nathan | 2021-08-03 21:32:18 | Re: archive status ".ready" files may be created too early |