Hello!
I'm interested in SELECT ... FOR SHARE 8.1 feature. I'd tried to measure performance degradation and got something about 30-60% for queries retrieve a lot of rows. Is it realistic estimation? Does this penalty depend on something (data types, triggers, foreign keys, whatever) significantly? Is any sort of lock escalation [and other unpreditable things] involved here?
Last question. What about ISOLATION LEVEL REPEATABLE READ syntax since non-exclusive locking for all SELECTs means [as far as I understand] nothing but REPEATABLE READ?
Thanks.
--
Best regards
Ilja Golshtein
---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your
message can get through to the mailing list cleanly
