From: | Devrim GUNDUZ <devrim(at)gunduz(dot)org> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Subject: | Re: SELECT FOR UPDATE NOWAIT and PostgreSQL 8.0 |
Date: | 2004-09-14 17:33:19 |
Message-ID: | Pine.LNX.4.61.0409142026390.8416@emo.org.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
On Mon, 13 Sep 2004, Simon Riggs wrote:
> Now we have LOCK TABLE ... NOWAIT; but I wonder whether we'll have the
> SELECT ... NOWAIT one. Today I got a request for this; and it was
> reported that this feature will be used in a huge project.
>
> Well, it shouldn't be too much of a patch - just cloning the code?
>
> Perhaps they can start in development without it and we'll patch it in
> later.
I learned that the code is ready. They'll change the code now.
>> Hmm... this seems the exact opposite of how I would tend to think
>> the feature
>> would be used... ie. you don't really care how long the query takes, just
>> that you can't get the lock.
>
> Agreed - and this is important! I thought we'd done NOWAIT on the SELECT...
>
> Oh well, 8.1 will be better still.
Bruce: Any TODO here? ;)
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org devrim.gunduz~linux.org.tr
http://www.tdmsoft.com
http://www.gunduz.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFBRythtl86P3SPfQ4RAg5+AJ9jdgkolYwBgeLhTBRMt0W0TGd8AwCeJQuM
95igCBca4aisP82g4374nxs=
=Yr9x
-----END PGP SIGNATURE-----
From | Date | Subject | |
---|---|---|---|
Next Message | Dennis Bjorklund | 2004-09-14 17:35:29 | Is select a transaction starting statement? |
Previous Message | Merlin Moncure | 2004-09-14 17:20:10 | Re: pg_locks view and user locks |