Skip site navigation (1) Skip section navigation (2)

Re: bgwriter never dies

From: Philip Warner <pjw(at)rhyme(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>,Neil Conway <neilc(at)samurai(dot)com>, Jan Wieck <JanWieck(at)Yahoo(dot)com>,pgsql-hackers(at)postgresql(dot)org
Subject: Re: bgwriter never dies
Date: 2004-02-26 05:48:24
Message-ID: 6.0.0.22.0.20040226164450.04323ea0@203.8.195.10 (view raw or flat)
Thread:
Lists: pgsql-hackers
At 04:01 PM 26/02/2004, Tom Lane wrote:
>there is no basis for assuming that a postmaster failure has
>anything to do with problems at the backend level....So my
>opinion is that "kill all the backends when the postmaster
>crashes" is a bad idea

Sounds fine. Then a system that will allow a new PM to start ASAP and serve 
other connections would be great. I assume that means an orderly shutdown & 
restart, but I can't see a way to make the restart work.


----------------------------------------------------------------
Philip Warner                    |     __---_____
Albatross Consulting Pty. Ltd.   |----/       -  \
(A.B.N. 75 008 659 498)          |          /(@)   ______---_
Tel: (+61) 0500 83 82 81         |                 _________  \
Fax: (+61) 03 5330 3172          |                 ___________ |
Http://www.rhyme.com.au          |                /           \|
                                  |    --________--
PGP key available upon request,  |  /
and from pgp.mit.edu:11371       |/ 


In response to

pgsql-hackers by date

Next:From: Jonathan ScottDate: 2004-02-26 06:09:07
Subject: Re: simple make check failures
Previous:From: Tom LaneDate: 2004-02-26 05:17:14
Subject: Re: simple make check failures

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group