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

pgsql: On systems that have setsid(2) (which should be just about

From: tgl(at)postgresql(dot)org (Tom Lane)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: On systems that have setsid(2) (which should be just about
Date: 2006-11-21 20:59:53
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committers
Log Message:
On systems that have setsid(2) (which should be just about everything except
Windows), arrange for each postmaster child process to be its own process
group leader, and deliver signals SIGINT, SIGTERM, SIGQUIT to the whole
process group not only the direct child process.  This provides saner behavior
for archive and recovery scripts; in particular, it's possible to shut down a
warm-standby recovery server using "pg_ctl stop -m immediate", since delivery
of SIGQUIT to the startup subprocess will result in killing the waiting
recovery_command.  Also, this makes Query Cancel and statement_timeout apply
to scripts being run from backends via system().  (There is no support in the
core backend for that, but it's widely done using untrusted PLs.)  Per gripe
from Stephen Harris and subsequent discussion.

Modified Files:
        xlog.c (r1.256 -> r1.257)
        bootstrap.c (r1.226 -> r1.227)
        autovacuum.c (r1.28 -> r1.29)
        bgwriter.c (r1.30 -> r1.31)
        pgarch.c (r1.26 -> r1.27)
        pgstat.c (r1.139 -> r1.140)
        postmaster.c (r1.502 -> r1.503)
        syslogger.c (r1.28 -> r1.29)
        proc.c (r1.180 -> r1.181)
        postgres.c (r1.517 -> r1.518)
        misc.c (r1.54 -> r1.55)

pgsql-committers by date

Next:From: Bruce MomjianDate: 2006-11-21 21:37:34
Subject: pgsql: Mention pgpool-II can do Clustering For Parallel Query Execution.
Previous:From: Bruce MomjianDate: 2006-11-21 18:31:57
Subject: pgsql: Update Statement-Based Replication Middleware docs to be more

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