AW: AW: timeout on lock feature - Mailing list pgsql-hackers

From Zeugswetter Andreas SB
Subject AW: AW: timeout on lock feature
Date
Msg-id 11C1E6749A55D411A9670001FA68796336828D@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
List pgsql-hackers
> > I envisioned:
> 
> >     SET TIMEOUT TO 10;
> >     UPDATE tab SET col = 3;
> >     RESET TIMEOUT
> 
> > Can't we get that work work properly?  Let the timeout only 
> apply to the
> > 'tab' table and none of the others.
> 
> As Henryk has implemented it, it WON'T only apply to the 'tab' table;
> it'll affect all locks grabbed anywhere, including those that the system
> locks internally.  That scares the heck out of me, Andreas' objections
> notwithstanding.

What exactly scares you ? Surely the deadlock resolution should
handle the above decision to ABORT in the same way it currently does.
If not we have something to fix, no?

Of course this might rather be something to consider for 7.2 and not 7.1.1.

Andreas


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Re: [PATCHES] Patch for PostgreSQL 7.0.3 to compile on Tru64 UNIX v5.0A
Next
From: Tom Lane
Date:
Subject: Re: Re: No printable 7.1 docs?