"Pablo Montilla" <melkor@adinet.com.uy> writes:
> What I've got is something like this:
> Session1> INSERT INTO Table VALUES(0);
> Session1> COMMIT;
> Session2> SELECT FROM Table;
> And Session2 is not gettint the values I've just commited.
I don't believe that can happen, unless you've made a programming
error.
(1) Are you waiting for the COMMIT response to come back before you
issue the other SELECT?
(2) Are you running the other transaction in serializable mode?
If so, it won't see commits that happened later than its own BEGIN.
regards, tom lane