First of all: the version of Postgres you're using is ancient.
Secondly: the default behaviour for postgres is to terminate
the sub-process when the connection gets dropped; this leads me
to believe that the problem is with your application, and trying
to fix the app by killing off postgres processes is daft (and I'm
being friendly here... ).
To assess your problem more efficiently we'd need to know more
about the environment, and how you use it.
Cheers,
Tink
|