Re: Locks/Committed Read Problem

Committed Read implies that it can only return committed data. Therefore, if one process has the row locked (always the case if it is updated and still in a transaction), then the other process can not read the row until it is committed or rolled back (the transaction is closed). If you want the read-only process to be allowed to access the row even while it is locked, use dirty read. The gotcha here is that you may get the before image or the after image (from process with transaction) depending on whether the buffers have been flushed or not.