| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, "wangsh(dot)fnst(at)fujitsu(dot)com" <wangsh(dot)fnst(at)fujitsu(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "Bharath Rupireddy" <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Greg Sabino Mullane <htamfids(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "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: | 2022-01-25 19:30:33 |
| Message-ID: | B6186047-CB98-49B1-A2CA-959057703788@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/25/22, 12:01 AM, "Michael Paquier" <michael(at)paquier(dot)xyz> wrote:
> So, where are we on this patch? It looks like there is an agreement
> that MaxBackends is used widely enough that it justifies the use of a
> separate function to set and get a better value computed. There may
> be other parameters that could use a brush up, but most known cases
> would be addressed here. v4 looks rather straight-forward, at quick
> glance.
I think the patch is in decent shape. There may be a few remaining
places where GetMaxBackends() is called repeatedly in the same
function, but IIRC v4 already clears up the obvious ones. I don't
know if this is worth worrying about too much, but I can create a new
version if you think it is important.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Blake, Geoff | 2022-01-25 19:57:33 | Re: Add spin_delay() implementation for Arm in s_lock.h |
| Previous Message | Robert Haas | 2022-01-25 19:30:01 | Re: autovacuum prioritization |