| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Shaun Thomas <sthomas(at)townnews(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: Cost limit. |
| Date: | 2001-05-18 17:00:39 |
| Message-ID: | 20289.990205239@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Shaun Thomas <sthomas(at)townnews(dot)com> writes:
>> Note you could implement such a time limit purely on the client side,
>> which might be an easier and more flexible way to go.
> That's just it. PHP (our front end) has a 30 second time limit we
> have not overridden. But we've found that after the PHP execution stops
> in disgust, the postgres thread keeps going until we restart the
> postgres back end.
Sounds like PHP is not actually trying to cancel the query when it
gives up waiting. Anyone care to go in and fix that?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Miguel Gonzalez | 2001-05-18 18:07:14 | password politic |
| Previous Message | Shaun Thomas | 2001-05-18 16:41:52 | Re: Cost limit. |