| From: | Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Logical replication launcher never been restarted when terminated |
| Date: | 2017-06-22 05:06:24 |
| Message-ID: | 20170622140624.e8338bfc.nagata@sraoss.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, 21 Jun 2017 15:17:20 -0400
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 6/21/17 13:03, Yugo Nagata wrote:
> > As I report in another thread[1], when the logical replication launcher
> > is terminated by SIGTERM, it never been restarted and we need to restart
> > the server to enable logical replication again.
> >
> > This is because the logical replication launcher exits with exitstatus 0,
> > so if it exits with status 1 it is restarted by the postmaster normally.
> > Attached is a simple patch to fix it in this way.
>
> Fixed, thanks!
Thanks!
>
> --
> Peter Eisentraut http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-06-22 05:08:30 | Re: pg_terminate_backend can terminate background workers and autovacuum launchers |
| Previous Message | Michael Paquier | 2017-06-22 05:04:42 | Re: Fast promotion not used when doing a recovery_target PITR restore? |