> On 12 January 2017 at 09:36, Robert Haas <robertmh...@gmail.com> wrote: >> One option is certainly to decide categorically that background >> workers are not connections, and therefore CountUserBackends() should >> ignore them and InitializeSessionUserId() shouldn't call it when the >> session being started is a background worker. That means that >> background workers don't count against the user connection limit, full >> stop.
I've attached a patch which intended to assist discussions on this topic. The patch adds some notes to the docs to mention that background workers and prepared xacts are not counted in CONNECTION LIMIT, it then goes on and makes CountUserBackends() ignore bgworkers. It was already ignoring prepared xacts. There's a bit of plumbing work to make the proc array aware of the background worker status. Hopefully this is suitable. I'm not all that close to that particular area of the code. -- David Rowley http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services
connection_limit_ignore_bgworkers_v1.patch
Description: Binary data
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
