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

pgsql: Don't set the signal handler for SIGQUIT on Windows.

From: heikki(at)postgresql(dot)org (Heikki Linnakangas)
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Don't set the signal handler for SIGQUIT on Windows.
Date: 2009-03-18 20:30:35
Message-ID: 20090318203035.1B53C754ADE@cvs.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Log Message:
-----------
Don't set the signal handler for SIGQUIT on Windows. Buildfarm shows that
reinstalling the default signal handler doesn't work as it is on Windows.
Presumably core dumps on SIGQUIT are not a problem on Windows, so rather
than figure out what header files or other changes are required to make it
work, just don't bother.

Modified Files:
--------------
    pgsql/contrib/pg_standby:
        pg_standby.c (r1.19 -> r1.20)
        (http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/contrib/pg_standby/pg_standby.c?r1=1.19&r2=1.20)

pgsql-committers by date

Next:From: Heikki LinnakangasDate: 2009-03-18 20:30:36
Subject: pgsql: Don't set the signal handler for SIGQUIT on Windows.
Previous:From: Tom LaneDate: 2009-03-18 20:18:19
Subject: pgsql: Be more clear about when to use gist__int_ops vs.

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