Re: Safe to kill idle connections? - Mailing list pgsql-general

From Francisco Reyes
Subject Re: Safe to kill idle connections?
Date
Msg-id 20051017081105.H12366@zoraida.natserv.net
Whole thread Raw
In response to Re: Safe to kill idle connections?  (Richard Huxton <dev@archonet.com>)
Responses Re: Safe to kill idle connections?  (Richard Huxton <dev@archonet.com>)
List pgsql-general
On Mon, 17 Oct 2005, Richard Huxton wrote:

> At a guess, PHPWiki is using persistent connections to PG, so you'll get one
> connection per Apache backend.

Thanks for the info. That may well be the problem.

> Alternatively, a small change in PHPWiki's code should clear it too (start
> with a search for pg_pconnect and try pg_connect instead).

Will do.

> It's perfectly safe to leave the idle connections there - they won't take up
> much in the way of resources.

How about when one needs to reload to read new postgresql.conf files. Will
iddle connections prevent the server from reloading?

Also, in the future if other programs do the same, is it safe to kill
these and if so what is the best way? kill command?

pgsql-general by date:

Previous
From: Devrim GUNDUZ
Date:
Subject: Re: Anybody using PostGIS?
Next
From: Douglas McNaught
Date:
Subject: Re: could not connect to the server error