pgsql: Don't set the signal handler for SIGQUIT on Windows. - Mailing list pgsql-committers

From heikki@postgresql.org (Heikki Linnakangas)
Subject pgsql: Don't set the signal handler for SIGQUIT on Windows.
Date
Msg-id 20090318203035.1B53C754ADE@cvs.postgresql.org
Whole thread Raw
List 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:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Be more clear about when to use gist__int_ops vs.
Next
From: heikki@postgresql.org (Heikki Linnakangas)
Date:
Subject: pgsql: Don't set the signal handler for SIGQUIT on Windows.