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

From Bruce Momjian
Subject Re: timeout on lock feature
Date
Msg-id 200104131828.OAA21993@candle.pha.pa.us
Whole thread Raw
In response to Re: timeout on lock feature  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> The appropriate way to do this given a LOCK TABLE option would be like
> 
>     BEGIN;
>     LOCK TABLE foo IN ROW EXCLUSIVE MODE WITH TIMEOUT n;
>     UPDATE foo SET ...;
>     COMMIT;
> 
> which restricts the scope of the timeout behavior to just the specific
> lock that the user is thinking of, and doesn't risk breaking fundamental
> system operations.

This is pretty tough because the user has to know the proper lock type,
right?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_dump ordering problem (rc4)
Next
From: Tom Lane
Date:
Subject: Re: Truncation of object names