From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [COMMITTERS] pgsql: Restart logical replication launcher when killed |
Date: | 2017-06-21 23:52:16 |
Message-ID: | 20170621235216.qekl7ocapfxi3w2d@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
On 2017-06-22 08:46:35 +0900, Michael Paquier wrote:
> On Thu, Jun 22, 2017 at 4:16 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
> > Restart logical replication launcher when killed
>
> - /* The logical replication launcher can be stopped at any time. */
> - proc_exit(0);
> + /* The logical replication launcher can be stopped at any time.
> + * Use exit status 1 so the background worker is restarted. */
> + proc_exit(1);
> I know I am noisy on the matter but... This comment format is not PG-like.
That's since been repaired by the new pgindent run. But what I'm a bit
confused about is why we're going for proc_exit() for replication
launchers when other types of processes simply FATAL out? Seems like a
weird change. It's not like it's not log-worthy if somebody kills the
launcher?
- Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2017-06-22 03:25:28 | pgsql: Teach pgrowlocks to check relkind before scanning |
Previous Message | Michael Paquier | 2017-06-21 23:46:35 | Re: [COMMITTERS] pgsql: Restart logical replication launcher when killed |
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2017-06-21 23:56:35 | Re: RLS in CTE incorrect permission failure |
Previous Message | Tom Lane | 2017-06-21 23:46:51 | Re: RLS in CTE incorrect permission failure |