Re: [PATCH] Transaction traceability - txid_status(bigint)
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Craig Ringer <craig@2ndquadrant.com>
Cc: Petr Jelinek <petr@2ndquadrant.com>, Simon Riggs <simon@2ndquadrant.com>, PostgreSQL Hackers <pgsql-hackers@postgresql.org>,
Andres Freund <andres@anarazel.de>, Jim Nasby <Jim.Nasby@bluetreble.com>
Date: 2016-09-16T13:28:54Z
Lists: pgsql-hackers
On Thu, Sep 15, 2016 at 8:52 PM, Craig Ringer <craig@2ndquadrant.com> wrote: > On 2 September 2016 at 23:29, Petr Jelinek <petr@2ndquadrant.com> wrote: > >> You could put it to txid.c where all the other txid stuff is in? > > Yeah, even though it's in adt/ I think it'll do. > > I thought I'd need get_xid_in_recent_past() for catalog_xmin hot > standby feedback, but upon closer examination the needed logic isn't > the same anymore. txid_status() wants to ensure clog lookups are safe > and limit by oldest xid, wheras the walsender doesn't actually care > about that and is just avoiding wrapped xids. > > I'm just going back to how it was, all in adt/txid.c, and making it > static again. We can move it and make it non-static if a need to do so > comes up. > > Attached rebased patch updated and vs master. You appear to have attached the wrong patch set. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Add a txid_status function.
- 857ee8e391ff 10.0 landed
-
Track the oldest XID that can be safely looked up in CLOG.
- ea42cc18c353 10.0 landed