| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: timeout on lock featurey |
| Date: | 2001-04-18 23:33:24 |
| Message-ID: | 200104182333.f3INXOx04659@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> 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
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Myers | 2001-04-19 01:09:46 | Re: timeout on lock feature |
| Previous Message | Mitch Vincent | 2001-04-18 22:32:07 | Re: CRN article not updated |