From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jeff <threshar@torgo.978.org>
Cc: pgsql-admin@postgresql.org
Subject: Re: preventing the effective fork bomb when restarting a high traffic server?
Date: Mon, 13 Dec 2004 17:18:09 -0500
Message-ID: <28598.1102976289@sss.pgh.pa.us> (raw)
In-Reply-To: <A62361DA-4D3C-11D9-8178-000D9366F0C4@torgo.978.org>
References: <A62361DA-4D3C-11D9-8178-000D9366F0C4@torgo.978.org>
Jeff <threshar@torgo.978.org> 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
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-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, threshar@torgo.978.org
Subject: Re: preventing the effective fork bomb when restarting a high traffic server?
In-Reply-To: <28598.1102976289@sss.pgh.pa.us>
References: <A62361DA-4D3C-11D9-8178-000D9366F0C4@torgo.978.org> <28598.1102976289@sss.pgh.pa.us>
* 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