Andres Freund wrote: > Hi all, > > I noticed the need to simply stop a bgworker after its work is done but > still have it restart in unusual circumstances like a crash. > Obviously I can just have it enter a loop where it checks its latch and > such, but that seems a bit pointless. > > Would it make sense to add an extra return value or such for that?
KaiGai also requested some more flexibility in the stop timing and shutdown sequence. I understand the current design that workers are always on can be a bit annoying. How would postmaster know when to restart a worker that stopped? -- Álvaro Herrera 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
