> What might be a reasonable alternative would be a BEGIN timeout: report > failure as soon as possible after N seconds unless the timer is reset, > such as by a commit. Such a timeout would be meaningful at the > database-interface level. It could serve as a useful building block > for application-level timeouts when the client environment has trouble > applying timeouts on its own. Now that is a nifty idea. Just put it on one command, BEGIN, and have it apply for the whole transaction. We could just set an alarm and do a longjump out on timeout. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
- Re: AW: [HACKERS] timeout on lock feature Bruce Momjian
- Re: AW: [HACKERS] timeout on lock feature Tom Lane
- [HACKERS] Re: AW: timeout on lock feature Henryk Szal
- Re: AW: [HACKERS] timeout on lock feature Tom Lane
- RE: AW: [HACKERS] timeout on lock feature Michael Ansley
- RE: AW: [HACKERS] timeout on lock feature Mikheev, Vadim
- AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- Re: AW: [HACKERS] timeout on lock feature Tom Lane
- Re: [HACKERS] timeout on lock feature Nathan Myers
- Re: [HACKERS] timeout on lock feature Bruce Momjian
- Re: [HACKERS] timeout on lock feature Nathan Myers
- Re: [HACKERS] timeout on lock feat... Bruce Momjian
- Re: [HACKERS] timeout on lock... Nathan Myers
- RE: AW: [HACKERS] timeout on lock feature Mikheev, Vadim
- Re: AW: [HACKERS] timeout on lock feature Bruce Momjian
- RE: AW: [HACKERS] timeout on lock feature Mikheev, Vadim
- Re: AW: [HACKERS] timeout on lock featurey Bruce Momjian
- AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB