Re: BUG #5915: OldSerXidAdd inflates pg_serial too much

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Heikki Linnakangas" <heikki(dot)linnakangas(at)enterprisedb(dot)com>
Cc: "YAMAMOTO Takashi" <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp>, <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #5915: OldSerXidAdd inflates pg_serial too much
Date: 2011-03-04 21:28:27
Message-ID: 4D71051B020000250003B4D3@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Christopher Head 2011-03-05 05:16:30 Re: BUG #5895: Ability to match more than just CN in client certificate
Previous Message Kevin Grittner 2011-03-04 21:16:51 Re: BUG #5915: OldSerXidAdd inflates pg_serial too much