Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Dilip Kumar <dilipbalaut(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Have SIGHUP instead of SIGTERM for config reload in logical replication launcher
Date: 2020-07-15 15:03:59
Message-ID: CALj2ACXFCOdwJyLFGxeXKMZ_1_r8zGPGzYGBo42d8uvkXSUEqw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>
> +1. I will commit this tomorrow unless someone thinks otherwise.
>

I think versions <= 12, have "pqsignal(SIGHUP,
logicalrep_launcher_sighup)", not sure why and which commit removed
logicalrep_launcher_sighup().

We might have to also backpatch this patch to version 13.

With Regards,
Bharath Rupireddy.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2020-07-15 15:04:28 Re: TAP tests and symlinks on Windows
Previous Message Alvaro Herrera 2020-07-15 15:03:33 Re: Postgres is not able to handle more than 4k tables!?