On Thu, Jul 19, 2018 at 3:42 PM, Andres Freund <and...@anarazel.de> wrote: > I don't think this reasoning actually applies for making HOT pruning > weaker as necessary for decoding. The xmin horizon on catalog tables is > already pegged, which'd prevent similar problems.
That sounds completely wrong to me. Setting the xmin horizon keeps tuples that are made dead by a committing transaction from being removed, but I don't think it will do anything to keep tuples that are made dead by an aborting transaction from being removed. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
