> 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.
In response to
pgsql-bugs by date
|Next:||From: Christopher Head||Date: 2011-03-05 05:16:30|
|Subject: Re: BUG #5895: Ability to match more than just CN in client
|Previous:||From: Kevin Grittner||Date: 2011-03-04 21:16:51|
|Subject: Re: BUG #5915: OldSerXidAdd inflates pg_serial too much|