| From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Szima Gábor <sygma(at)axelero(dot)hu>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 |
| Date: | 2004-09-20 12:41:41 |
| Message-ID: | 414ED005.5070707@pse-consulting.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian wrote:
> Interesting. So it times out a transaction to release its locks. Does
> it time from the start of the transaction? I assume so. We do have
> statment_timeout so maybe transaction_timeout would be the proper name.
> Timing out on just the idle state seems strange to me.
Timing out on the start of the transaction isn't a good idea; what about
long running transactions? You'd have to set the timeout very high (lets
say to have nightly imports) which would make the "idle in transaction
and not responding any more" errors detected very late in online situations.
So the timeout should start after each statement's completion.
Regards,
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D'Arcy J.M. Cain | 2004-09-20 13:38:45 | PostgreSQL 7.4 runs slower than 7.3 |
| Previous Message | Bruce Momjian | 2004-09-20 12:30:55 | Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 |