Skip site navigation (1) Skip section navigation (2)

pgsql: Don't intercept SIGQUIT as a signal to trigger failover; that's

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't intercept SIGQUIT as a signal to trigger failover; that's
Date: 2009-03-18 19:27:30
Message-ID: 20090318192730.6BA61754AE1@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Don't intercept SIGQUIT as a signal to trigger failover; that's what
postmaster uses for immediate shutdown. Trap SIGUSR1 as the preferred
signal for that.

Per report by Fujii Masao and subsequent discussion on -hackers.

Tags:
----
REL8_3_STABLE

Modified Files:
--------------
    pgsql/contrib/pg_standby:
        pg_standby.c (r1.10.2.3 -> r1.10.2.4)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_standby/pg_standby.c?r1=1.10.2.3&r2=1.10.2.4)

pgsql-committers by date

Next:From: Tom LaneDate: 2009-03-18 20:18:19
Subject: pgsql: Be more clear about when to use gist__int_ops vs.
Previous:From: Heikki LinnakangasDate: 2009-03-18 19:27:28
Subject: pgsql: Don't intercept SIGQUIT as a signal to trigger failover; that's

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group