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
Tigran Mkrtchyan wrote:
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
Dear PostgreSQL gurus,
I got a incorrect or unexpected behavior in concurrent environment.
Luckily, I was able to localize it and create an example:
My setup:
Postgres 8.2 ( with 8.1 the same effect )
Linux ( with Solaris the same effect )
java 1.5, JDBC driver 8.2-504.jdbc3 ( with
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
