From: | Hans-Jürgen Schönig <postgres(at)cybertec(dot)at> |
---|---|
To: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
Cc: | blind(at)xythos(dot)com, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCHES] NO WAIT ... |
Date: | 2004-02-19 01:17:08 |
Message-ID: | 40340E94.2000700@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Tatsuo Ishii wrote:
>>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
>
> ---------------------------(end of broadcast)---------------------------
> TIP 8: explain analyze is your friend
That would be great.
Many people are asking for that.
Maybe I have time to implement that for SELECT FOR UPDATE.
Hans
--
Cybertec Geschwinde u Schoenig
Schoengrabern 134, A-2020 Hollabrunn, Austria
Tel: +43/2952/30706 or +43/664/233 90 75
www.cybertec.at, www.postgresql.at, kernel.cybertec.at
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2004-02-19 04:16:13 | unqualified function calls in system_views.sql |
Previous Message | Tatsuo Ishii | 2004-02-19 01:00:45 | Re: [PATCHES] NO WAIT ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Tatsuo Ishii | 2004-02-19 05:47:59 | Re: [PATCHES] NO WAIT ... |
Previous Message | Tatsuo Ishii | 2004-02-19 01:00:45 | Re: [PATCHES] NO WAIT ... |