| From: | "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com> |
|---|---|
| To: | Mario Splivalo <mario(dot)splivalo(at)mobart(dot)hr> |
| Cc: | Pgsql performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: SELECT FOR UPDATE performance is bad |
| Date: | 2006-04-20 16:50:02 |
| Message-ID: | 20060420165002.GY49405@pervasive.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, Apr 19, 2006 at 10:20:54AM +0200, Mario Splivalo wrote:
> This works perfectly, but sometimes the game has no codes, and I still
> need to know exactley who came first, who was second, and so on... So a
> locking table as Tom suggested is, I guess, a perfect solution for my
> situation...
Depending on your performance requirements, you should look at
contrib/userlock as well, since it will probably be much more performant
than locking a row in a table.
--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2006-04-20 16:55:32 | Re: Quick Performance Poll |
| Previous Message | Will Reese | 2006-04-20 16:48:36 | Slow deletes in 8.1 when FKs are involved |