X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 20EB23A6230 for ; Mon, 13 Dec 2004 22:18:14 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 02996-04 for ; Mon, 13 Dec 2004 22:18:08 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 214863A622E for ; Mon, 13 Dec 2004 22:18:10 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iBDMI9px028599; Mon, 13 Dec 2004 17:18:10 -0500 (EST) To: Jeff Cc: pgsql-admin@postgresql.org Subject: Re: preventing the effective fork bomb when restarting a high traffic server? In-reply-to: References: Comments: In-reply-to Jeff message dated "Mon, 13 Dec 2004 14:24:46 -0500" Date: Mon, 13 Dec 2004 17:18:09 -0500 Message-ID: <28598.1102976289@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.006 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/117 X-Sequence-Number: 15703 Jeff writes: > The problem I'm encountering is when I restart PG for whatever reason > it takes it a long time to come back fully online: the reason: the > machine is dealing with over 100 connection attempts / second while > trying to replay the logical logs. Um, perhaps you should allow the database to shut down normally, instead of kill -9 or whatever you're using? There should not be any log replay needed after an ordinary restart. In any case, I think the best solution would be to fix your frontends to wait a little bit between connection attempts... regards, tom lane