Tom,
> No, I'd not expect the second stop to fail; and I can't reproduce any
> such problem here.
I've had it happen once.
> The known bug might cause the *first* stop to fail; it basically
> triggers if you have a client that sits idle for a long time (while
> other sessions are doing work) and still remains idle after the shutdown
> command comes.
So ... the workaround for 7.2.4 would be to have a server-side script hunt for
idle connections after shutdown and kill -9 them?
--
-Josh Berkus
Aglio Database Solutions
San Francisco
