I wrote: > I think what we're protecting against is disk I/O at COMMIT time, > not transaction startup. One more thought on this -- on a properly configured server, this code should rarely be exercised unless there is a long-running READ WRITE transaction. The delay, if any, would be on the connection which is committing that long running transaction. -Kevin
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
