>I believe 20 seconds is the standard number --- that's plenty for
>Postgres.
>
Not always. More than once I have had a postgresql connection hung up
that will stop the main postmaster from dying on TERM. However the
machine will eventually kill it hard and thus could produce during restart.
Sincerely,
Joshua Drake
> (I know that it is about 20 seconds on OS X, because
>that's how much time tended to get added to the shutdown procedure
>back when OS X 10.0 had that shutdown bug that prevented the postmaster
>from forking a shutdown subprocess.)
>
>The fact that the number isn't readily configurable is indeed a PITA.
>In a previous lifetime I ran a data-collection application that needed
>more than 20 seconds to shut down, and so would not exit cleanly if
>you didn't have a shutdown script step that would wait for it. But
>I don't see it as a problem for Postgres.
>
> regards, tom lane
>
>---------------------------(end of broadcast)---------------------------
>TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to majordomo@postgresql.org)
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-222-2783 - jd@commandprompt.com - http://www.commandprompt.com
Editor-N-Chief - PostgreSQl.Org - http://www.postgresql.org
