| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Henryk Szal <szal(at)doctorq(dot)com(dot)pl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | AW: AW: AW: timeout on lock feature |
| Date: | 2001-04-17 15:37:47 |
| Message-ID: | 11C1E6749A55D411A9670001FA68796336828F@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > The timeout will be useful to let the client or user decide on an
> > alternate course of action other that killing his application (without
> > the need for timers or threads in the client program).
>
> This assumes (without evidence) that the client has a good idea of what
> the timeout limit ought to be.
Yes, the application programmer would need to know how long his users
are willing to wait before they start to "hammer at their monitors, kick their pc's
or throw the mouse across the room :-O". It must be made clear that it is very counter
productive to use too short timeouts.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Louis-David Mitterrand | 2001-04-17 16:00:05 | row archiving trigger function |
| Previous Message | Francisco Alvarez | 2001-04-17 15:32:30 | doubts |