Re: preventing the effective fork bomb when restarting a high traffic server? - Mailing list pgsql-admin

From Tom Lane
Subject Re: preventing the effective fork bomb when restarting a high traffic server?
Date
Msg-id 28598.1102976289@sss.pgh.pa.us
Whole thread Raw
In response to preventing the effective fork bomb when restarting a high traffic server?  (Jeff <threshar@torgo.978.org>)
List pgsql-admin
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

pgsql-admin by date:

Previous
From: Joe Conway
Date:
Subject: Re: plperl loading
Next
From: Tom Lane
Date:
Subject: Re: From latin9 to sql_ascii??