In article <423F09CF.2030008@alexandcarmen.com>,
Alex Adriaanse <alex@alexandcarmen.com> writes:
> I think that would greatly decrease the chances of a race condition
> occurring, but I don't think it'd solve it. What if 150 other
> revisions occur between a row update and its corresponding commit?
How about the following:
* Use a TIMESTAMP rather than a SERIAL
* Set this timestamp to NULL in your INSERT/UPDATE trigger
* Use a cron job to set the timestamp to current_timestamp when it's NULL
This way the client would lag behind somewhat, depending on the cron
job frequency, but it should not miss a change.