| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | blind(at)xythos(dot)com |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [PATCHES] NO WAIT ... |
| Date: | 2004-02-19 01:00:45 |
| Message-ID: | 20040219.100045.41631437.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> I agree with Tom here. I have used the Oracle NOWAIT feature in the
> past and think it is a great feature IMHO. But when you need to use it,
> you want it to apply very specifically to a single statement. Using a
> sledge hammer when you need a tweezers isn't the right way to go.
Once I have written patches for 7.3 to implement this feature for LOCK
statement. For example:
test=# LOCK TABLE sales NO WAIT;
ERROR: Cannot aquire relation lock
If there's enough interest, I will modify and submit it for 7.5.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Jürgen Schönig | 2004-02-19 01:17:08 | Re: [PATCHES] NO WAIT ... |
| Previous Message | Glen Parker | 2004-02-19 00:06:40 | Index scan ordering (performance) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hans-Jürgen Schönig | 2004-02-19 01:17:08 | Re: [PATCHES] NO WAIT ... |
| Previous Message | Jan Wieck | 2004-02-18 22:09:39 | Re: [PATCHES] NO WAIT ... |