| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: timeout on lock featurey |
| Date: | 2001-04-18 20:13:28 |
| Message-ID: | 200104182013.f3IKDSd19112@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
[ Charset ISO-8859-1 unsupported, converting... ]
> > One idea Tom had was to make it only active in a transaction,
> > so you do:
> >
> > BEGIN WORK;
> > SET TIMEOUT TO 10;
> > UPDATE tab SET col = 3;
> > COMMIT
> >
> > Tom is concerned people will do the SET and forget to RESET
> > it, causing all queries to be affected by the timeout.
>
> And what? Queries would be just aborted. It's not critical event
> to take responsibility from user.
Hey, I agree. If the users wants the TIMEOUT, give it to them.
--
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 | Bruce Momjian | 2001-04-18 20:16:18 | Re: Re: No printable 7.1 docs?y |
| Previous Message | Bruce Momjian | 2001-04-18 19:52:58 | Re: Another news story in need of 'enlightenment' |