| 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: | 2013-01-02 16:28:19 |
| Message-ID: | 20130102162819.GA5008@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I committed this with minor tweaks to avoid having to scan the
registered workers list on each registration. Opinions on this error
report are still welcome:
> + ereport(LOG,
> + (errcode(ERRCODE_CONFIGURATION_LIMIT_EXCEEDED),
> + errmsg("too many background workers"),
> + errdetail("Up to %d background workers can be registered with the current settings.",
> + MAX_BACKENDS - (MaxConnections + autovacuum_max_workers + 1))));
Thanks to everyone for their input --- and happy 2013 hacking to all.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitriy Igrishin | 2013-01-02 16:30:05 | Re: allowing multiple PQclear() calls |
| Previous Message | Heikki Linnakangas | 2013-01-02 16:23:08 | Re: Minor fix in 'clean' action of 'src/backend/Makefile' |