This option will be OPTIONAL. Tom Lane wrote in message <[EMAIL PROTECTED]>... >Bruce Momjian <[EMAIL PROTECTED]> writes: >> Added to TODO: >> * Add SET parameter to timeout if waiting for lock too long > >I repeat my strong objection to any global (ie, affecting all locks) >timeout. Such a "feature" will have unpleasant consequences. > > regards, tom lane > >---------------------------(end of broadcast)--------------------------- >TIP 5: Have you checked our extensive FAQ? > >http://www.postgresql.org/users-lounge/docs/faq.html ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
- AW: [HACKERS] timeout on lock feature Zeugswetter Andreas SB
- Re: AW: [HACKERS] timeout on lock feature Bruce Momjian
- Re: AW: [HACKERS] timeout on lock feature Tom Lane
- Re: AW: [HACKERS] timeout on lock feat... 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 featurey Bruce Momjian
- Re: [HACKERS] timeout on lock feat... Nathan Myers
- Re: [HACKERS] timeout on lock... Bruce Momjian