Greg Stark <st...@enterprisedb.com> wrote: > If you can never know for sure that you've written your transaction > safely Whoa! I just noticed this phrase on a re-read. I think there might be some misunderstanding here. You can be sure you've written your transaction safely just as soon as your COMMIT returns without error. Perhaps you're getting confused because under the non-blocking approach, each transaction's read locks (if any) continue to be tracked until all concurrent transactions terminate in order to determine if some *other* transaction might need to be rolled back. -Kevin
-- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
