Dynamic Background Workers and clean exit
Hello,
I've been recently doing some work with dynamic bgworkers and noticed
that I have no way of saying "I am done now and want to exit cleanly"
because bgworkers get restarted automatically on exit code 0 no matter
what is the restart interval set to.
I understand the rationale for this behavior when using static bgworkers
which are meant to run forever, but dynamic ones are spawned dynamically
by code so they should also be able to terminate cleanly as they have
presumably finite work to do. Also I think the clean shutdown of dynamic
bgworker should not be logged (or at least not with the same log level
as it is now) since it's business as usual.
Since the dyanamic bgworkers are new in 9.4 the behavior can still be
changed.
Thoughts?
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
On Wed, Apr 16, 2014 at 5:27 AM, Petr Jelinek <petr@2ndquadrant.com> wrote:
Hello,
I've been recently doing some work with dynamic bgworkers and noticed that I
have no way of saying "I am done now and want to exit cleanly" because
bgworkers get restarted automatically on exit code 0 no matter what is the
restart interval set to.I understand the rationale for this behavior when using static bgworkers
which are meant to run forever, but dynamic ones are spawned dynamically by
code so they should also be able to terminate cleanly as they have
presumably finite work to do. Also I think the clean shutdown of dynamic
bgworker should not be logged (or at least not with the same log level as it
is now) since it's business as usual.Since the dyanamic bgworkers are new in 9.4 the behavior can still be
changed.Thoughts?
See the other thread where this is being discussed...
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers