3 ms·
Indeed, and now() is often good enough, if not better, as it represents the conditions at the time that the logic was executed. The author needs to examine car
by mjevans 11y ago
Indeed, and now() is often good enough, if not better, as it represents the conditions at the time that the logic was executed.
The author needs to examine carefully why a value is being updated so many times within a single transaction (first example provided), which by it's own nature is an atomic change (there's no reason to write the middle states to disk as it'll either commit or it won't).
Second the author provides a multiple clients (writers) example. In this case if the ordering is important a LOCK is likely required; however it is more likely that consistency is required (in this case likely the psql specific functions).