From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: fix bgworkers in EXEC_BACKEND |
Date: | 2012-12-27 20:46:45 |
Message-ID: | 20121227204645.GD4238@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Heikki Linnakangas wrote:
> Might be cleaner to directly assign the correct value to MaxBackends
> above, ie. "MaxBackends = MaxConnections + newval + 1 +
> GetNumShmemAttachedBgworkers()". With a comment to remind that it
> needs to be kept in sync with the other places where that
> calculation is done, in guc.c. Or put that calculation in a new
> function and call it above and in guc.c.
>
> Thinking about this some more, it might be cleaner to move the
> responsibility of setting MaxBackends out of guc.c, into
> postmaster.c. The guc machinery would set max_connections and
> autovacuum_max_workers as usual, but not try to set MaxBackends.
> After reading the config file in postmaster.c, calculate
> MaxBackends.
Here's a small patch that applies on top of yours. Do you intend to
commit this? If not, let me know and I'll do it.
Thanks.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
Attachment | Content-Type | Size |
---|---|---|
calculate-MaxBackends-in-postmaster-inc.patch | text/x-diff | 855 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Fabrízio de Royes Mello | 2012-12-27 22:58:36 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
Previous Message | Tom Lane | 2012-12-27 19:08:11 | Re: fix bgworkers in EXEC_BACKEND |