| From: | Jie Liang <jie(at)stbernard(dot)com> |
|---|---|
| To: | 'Bruce Momjian' <pgman(at)candle(dot)pha(dot)pa(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'admin-sql(at)postgresql(dot)org'" <admin-sql(at)postgresql(dot)org>, pgsql-sql(at)postgresql(dot)org |
| Subject: | dead session terminate |
| Date: | 2002-03-29 22:08:04 |
| Message-ID: | 7C760DAA511DC74B99E7D22189F786F1906DE2@MAIL01.stbernard.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
I don't how to put this question in a right way:
I have a web application client to communicate with postgreSQL-7.1.3, in the
case
the application get crash, which sometime happens.
The GUI of my application is disappear, I check my backend process, the
connection
which was done by my application is still there, is there a programatic way,
I can
cleanup those dead sessions, does postgreSQL have a way to terminate those
dead
sessions by timeout?
My current solution is to use 'kill pid' under FreeBSD4.3, I don't think
it's
a good solution.
The side effect of exiting those dead session is to keep my user waiting,
I don't know why, but it does, I think it's wierd.
Thanks.
Jie Liang
Software Engineer
St. Bernard Software
16882 W. Bernardo Dr.
San Diego, CA 92127
Tel: 858-524-2134
Fax:858-676-2228
jie(at)stbernard(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-03-29 23:12:46 | Re: system tables |
| Previous Message | Hunter, Ray | 2002-03-29 16:08:05 | Optimization Advice |