Zeugswetter Andreas SB <[EMAIL PROTECTED]> writes:
> 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. I think this "feature" has no real use
other than encouraging application programmers to shoot themselves in
the foot. I see no reason that we should make it easy to misdesign
applications.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
- AW: AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- AW: AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- Re: AW: AW: [HACKERS] timeout on lock feat... Tom Lane
- Re: [HACKERS] timeout on lock feature Nathan Myers
- Re: [HACKERS] timeout on lock feat... Theo Kramer
- AW: AW: [HACKERS] timeout on lock feature Tom Lane
- AW: AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- RE: AW: AW: [HACKERS] timeout on lock feature Mikheev, Vadim
- [HACKERS] Re: AW: AW: timeout on lock feat... Henryk Szal
- Re: [HACKERS] Re: AW: AW: timeout on l... Bruce Momjian
- AW: AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- [HACKERS] theory of distributed transactio... Oliver Seidel
