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 eBIKGQ613452 for ; Mon, 18 Dec 2000 15:16:26 -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 eBIKGQC01390; Mon, 18 Dec 2000 15:16:26 -0500 (EST) To: Mathijs Brands cc: Ian Lance Taylor , pgsql-hackers@postgresql.org Subject: Re: Re: [SQL] PostgreSQL crashes on me :( In-reply-to: <20001218202807.B6174@ilse.nl> References: <20001217215118.D64770@ilse.nl> <21339.977111275@sss.pgh.pa.us> <20001218173340.29569.qmail@daffy.airs.com> <20037.977161232@sss.pgh.pa.us> <20001218202807.B6174@ilse.nl> Comments: In-reply-to Mathijs Brands message dated "Mon, 18 Dec 2000 20:28:07 +0100" Date: Mon, 18 Dec 2000 15:16:26 -0500 Message-ID: <1387.977170586@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/778 X-Sequence-Number: 2299 Mathijs Brands writes: > I've worked around the situation by running a small script that continually > monitors postgres and takes appropriate action if postgres shuts down. I'm > assuming this problem won't lead to any data corruption. Hm. The problem here is that when the postmaster crashes, it probably doesn't take down the old backends with it. So if you auto-restart the postmaster, you may have two sets of backends that don't know about each other. That would be A Bad Thing. If your script kills off all the backends it can find before starting the new postmaster, that should work OK. A better solution would be to back-patch my errno fix into 7.0.3. You can see the diff as it stands for current sources at http://www.postgresql.org/cgi/cvsweb.cgi/pgsql/src/backend/postmaster/postmaster.c.diff?r1=1.198&r2=1.199&f=c The additions to reaper() are probably the only part you really need. regards, tom lane