Hi Bharath, Scott, Bharath's v11 removes the duplicated classifier by recording the inputs inside ComputeXidHorizonsInternal(), which addresses the concern Horiguchi, Sami and Bharath raised previously, and an xid8 xmin makes the obvious ORDER BY work.
One thing I'd like to keep from v10 is the xid column. In v11 a backend row's xmin is the older of its xid and xmin, so a backend that owns the oldest xid and backends that merely took snapshots after it look the same. With one idle-in-transaction session and twenty readers whose xmin equals its xid, that's twenty-one identical rows, and only one of them is worth terminating. Scott added xid in v5 for that reason. The proc's xid is still available at the point where v11 records its inputs, so keeping it would cost one field in XidHorizonProc and one column. Regards, Surya Poondla
