database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-07-30 11:03:19 +03:00
Code Activity

Fix all the server-side SIGQUIT handlers (grumble ... why so many identical

Browse Source 
copies?) to ensure they really don't run proc_exit/shmem_exit callbacks,
as was intended.  I broke this behavior recently by installing atexit
callbacks without thinking about the one case where we truly don't want
to run those callback functions.  Noted in an example from Dave Page.
This commit is contained in:
Tom Lane
2009-05-15 15:56:39 +00:00
parent abc924519a
commit 4616d57dad
6 changed files with 76 additions and 34 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
src/backend/storage/ipc/ipc.c
View File

@ -13,7 +13,7 @@
*
*
* IDENTIFICATION
* $PostgreSQL: pgsql/src/backend/storage/ipc/ipc.c,v 1.103 2009/05/05 20:06:07 tgl Exp $
* $PostgreSQL: pgsql/src/backend/storage/ipc/ipc.c,v 1.104 2009/05/15 15:56:39 tgl Exp $
*
*-------------------------------------------------------------------------
*/
@ -166,7 +166,8 @@ proc_exit_prepare(int code)
/* do our shared memory exits first */
shmem_exit(code);
elog(DEBUG3, "proc_exit(%d)", code);
elog(DEBUG3, "proc_exit(%d): %d callbacks to make",
code, on_proc_exit_index);
/*
* call all the registered callbacks.
@ -193,7 +194,8 @@ proc_exit_prepare(int code)
void
shmem_exit(int code)
{
elog(DEBUG3, "shmem_exit(%d)", code);
elog(DEBUG3, "shmem_exit(%d): %d callbacks to make",
code, on_shmem_exit_index);
/*
* call all the registered callbacks.