Subject Question on classic
Author Ann W. Harrison
Somebody on the support list raised an issue around the
visibility of committed transactions. He's got a multi-
threaded application, using separate connections for each
thread and, I believe, Classic architecture. His
transactions are read-committed.

He stores a record in thread1 and commits it, then wakes
thread2. Thread2 doesn't immediately see the new record,
but does eventually. In thinking it over, I'm not at all
sure how or when the state of newly committed transactions
is conveyed to separate classic processes. Do you know?

Obviously, when the current TIP is read, but what would
force a process to read the TIP after another process
changes it?