Does it mean that I have to commit after each select statement?
Here what the manual says:
------------
Description
COMMIT commits the current transaction. All changes made by the transaction
become visible to others and are guaranteed to be durable if a crash occurs.
-----------
Does select produces some changes?
Regards,
Tigran.
Tom Lane wrote:
Tigran Mkrtchyan <[EMAIL PROTECTED]> writes:
I got a incorrect or unexpected behavior in concurrent environment.
This is not a bug, nor even surprising. Since you haven't committed
the second transaction, there are a growing number of
dead-but-not-recyclable versions of the updated row. The active client
has to check each of these versions during its primary key uniqueness
check during each update.
regards, tom lane
--
________________________________________________________________________
Tigran Mkrtchyan DESY, IT,
[EMAIL PROTECTED] Notkestrasse 85,
Tel: + 49 40 89983946 Hamburg 22607,
Fax: + 49 40 89984429 Germany.
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
