| 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:35:13 |
| Message-ID: | 005905A1-6CAC-4C25-A08A-E2B8934AA618@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 8/2/21, 3:12 PM, "Andres Freund" <andres(at)anarazel(dot)de> wrote:
> I think this is overblown. We already size resources *after*
> shared_preload_libraries' _PG_init() runs, because that's the whole point of
> shared_preload_libraries. What's proposed in this thread is to *disallow*
> increasing resource usage in s_p_l _PG_init(), to make one specific case
> simpler - but it'll actually also make things more complicated, because other
> resources will still only be sized after all of s_p_l has been processed.
True. Perhaps the comments should reference the possibility that a
library will adjust resource usage to explain why
InitializeMaxBackends() is where it is.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2021-08-02 22:38:19 | Re: Make relfile tombstone files conditional on WAL level |
| Previous Message | Melanie Plageman | 2021-08-02 22:25:56 | Re: pg_stat_bgwriter.buffers_backend is pretty meaningless (and more?) |