|From:||Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>|
|To:||Markus Wanner <markus(at)bluegap(dot)ch>|
|Cc:||kaigai(at)kaigai(dot)gr(dot)jp, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org>|
|Subject:||Re: Review: Extra Daemons / bgworker|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
So here's version 8. This fixes a couple of bugs and most notably
creates a separate PGPROC list for bgworkers, so that they don't
interfere with client-connected backends.
I tested starting 1000 non-shmem attached bgworkers -- postmaster
doesn't break a sweat. Also running 200 backend-connected bgworkers
works fine (assuming they do nothing). This is on my laptop, which is a
dual-core Intel i5 processor.
One notable thing is that I had to introduce this in the postmaster
* process any libraries that should be preloaded at postmaster start
* If loadable modules have added background workers, MaxBackends needs to
* be updated. Do so now.
if (GetNumShmemAttachedBgworkers() > 0)
GetConfigOption("max_connections", false, false),
Note the intention here is to re-run the GUC assign hook for
max_connections (hence the commented out hypothetical call to do so).
Obviously, having to go through GetConfigOption and SetConfigOption is
not a nice thing to do; we'll have to add some new entry point to guc.c
for this to have a nicer interface.
(I also observed that it's probably a good idea to have something like
FunctionSetConfigOption for the places that are currently calling
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
|Next Message||Robert Haas||2012-12-03 21:46:20||Re: visibilitymap_count() at the end of vacuum|
|Previous Message||Andrew Dunstan||2012-12-03 21:02:37||Re: pgsql: Add mode where contrib installcheck runs each module in a separa|