| From: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
|---|---|
| To: | Shridhar Daithankar <shridhar_daithankar(at)persistent(dot)co(dot)in> |
| Cc: | Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-general(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Subject: | Re: "Expiring" transactions? |
| Date: | 2003-09-25 19:18:23 |
| Message-ID: | Pine.LNX.4.21.0309252004010.20483-100000@ponder.fairway2k.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, 25 Sep 2003, Shridhar Daithankar wrote:
> Gaetano Mendola wrote:
>
> > Bruce Momjian wrote:
> >> We have statement_timeout, but not transaction_timeout.
> > Could be nice have it, once I forgot to do a commit and I
> > left my desk, the day after all the DB was hanged by that opened
> > transaction.
>
> Probably it could detect idle time and disconnect.. That could be used to roll
> back automatically..
I'd be unhappy with the commit part of the original request for commit or
rollback and in the first instance wouldn't this be a candidate for the client
app. to perform?
Obviously the server may not detect if the client just goes away, unless
keepalive is on, but only the client knows that the user isn't waving the mouse
around the screen looking for that bit of information needed to complete the
query underconstruction.
--
Nigel J. Andrews
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Richard Huxton | 2003-09-25 19:39:31 | Re: About GPL and proprietary software |
| Previous Message | Ron Johnson | 2003-09-25 19:13:27 | Re: career in SQL/Database administration |