From: | Csaba Nagy <nagy(at)ecircle-ag(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Martijn van Oosterhout <kleptog(at)svana(dot)org>, Kynn Jones <kynnjo(at)gmail(dot)com>, Postgres general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: How to force disconnections from a Perl script? |
Date: | 2007-02-20 08:54:19 |
Message-ID: | 1171961658.3101.315.camel@coppola.muc.ecircle.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, 2007-02-20 at 03:43, Tom Lane wrote:
> Nonsense. pg_stat_activity + "kill -TERM" should solve this problem
> reasonably well. Some of us don't trust kill -TERM 100%, which is why
> it's not currently exposed as a standard function, but if you're using
> a reasonably recent PG release it's probably safe.
Oh, OK... so pg_stat_activity shows all connections now ? Or it was
always like that ? For some reason I thought it will only show
connections where a transaction is in progress. Idle can mean there is
nothing executing at all... are those shown too ?
Cheers,
Csaba.
From | Date | Subject | |
---|---|---|---|
Next Message | Rafa Comino | 2007-02-20 10:41:54 | Having performance problems with TSearch2 |
Previous Message | Devrim GUNDUZ | 2007-02-20 08:20:31 | Re: RPM compat-postgresql-libs-4-2 for IA-64 |