Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eBIIII606343 for ; Mon, 18 Dec 2000 13:18:18 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eBIIIQL20259; Mon, 18 Dec 2000 13:18:26 -0500 (EST) To: Ian Lance Taylor cc: pgsql-hackers@postgresql.org Subject: Re: 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> Comments: In-reply-to Ian Lance Taylor message dated "18 Dec 2000 09:58:02 -0800" Date: Mon, 18 Dec 2000 13:18:26 -0500 Message-ID: <20256.977163506@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/773 X-Sequence-Number: 2294 Ian Lance Taylor writes: > 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? I thought about that, but it doesn't seem like a cleaner solution. Basically you'd have to figure a tradeoff between wasted cycles in the postmaster and time delay to respond to a crashed backend. And there's no good tradeoff there. If you have a backend crash, you want to shut down the other backends ASAP, before they have a chance to propagate any shared-memory corruption that the failed backend might've created. The entire exercise is probably pointless if the postmaster twiddles its thumbs for awhile before killing the other backends. regards, tom lane