| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: putting a bgworker to rest |
| Date: | 2013-04-23 14:59:43 |
| Message-ID: | 20130423145943.GL2169@eldon.alvh.no-ip.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2013-04-23 15:08:34 | Re: Performance with the new security release? |
| Previous Message | Alvaro Herrera | 2013-04-23 14:51:06 | Re: Couple of issues with pg_xlogdump |