pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ian Lance Taylor <ian@airs.com>
To: tgl@sss.pgh.pa.us
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re: [SQL] PostgreSQL crashes on me :(
Date: 18 Dec 2000 09:58:02 -0800
Message-ID: <20001218175802.29750.qmail@daffy.airs.com> (raw)
In-Reply-To: <19085.977154107@sss.pgh.pa.us>
References: <20001217215118.D64770@ilse.nl>
	<21339.977111275@sss.pgh.pa.us>
	<20001217230141.A28714@store.zembu.com>
	<19085.977154107@sss.pgh.pa.us>

   Date: Mon, 18 Dec 2000 10:41:47 -0500
   From: Tom Lane <tgl@sss.pgh.pa.us>

   ncm@zembu.com (Nathan Myers) writes:
   > Sounds like a TODO list item: eliminate syscalls from signal handlers.

   After looking at it some more, I think that's a lot easier said than
   done.  We could try writing the postmaster's SIGCHLD routine in the 
   same style currently used for SIGHUP --- ie, signal handler just sets
   a flag that's examined by the main loop in ServerLoop --- but I don't
   see any way to guarantee timely response if we do that.  If the SIGCHLD
   happens just before we reach the select() then the select() will block,
   and we won't respond to the dying child until the next connection
   request arrives or some other signal happens.  That's OK under normal
   scenarios, but highly not OK when a backend has crashed.

   Any thoughts on a cleaner solution?

One way to avoid this race condition is to set a timeout on the
select.  What is the maximum acceptable time for a timely response?
Would executing a few instructions at that time interval impose an
unacceptable system load?  (Naturally no timeout should be used if
there are no child processes.)

Ian



view thread (12+ messages)  latest in thread

Message-ID: <20001218175802.29750.qmail@daffy.airs.com>
Permalink:  ../20001218175802.29750.qmail@daffy.airs.com/
Also on:    postgresql.org/message-id/20001218175802.29750.qmail@daffy.airs.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-sql@postgresql.org
  Cc: ian@airs.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
  Subject: Re: [SQL] PostgreSQL crashes on me :(
  In-Reply-To: <20001218175802.29750.qmail@daffy.airs.com>
  References: <20001217215118.D64770@ilse.nl> <21339.977111275@sss.pgh.pa.us> <20001217230141.A28714@store.zembu.com> <19085.977154107@sss.pgh.pa.us> <20001218175802.29750.qmail@daffy.airs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox