On July 23, 2018 9:11:13 AM PDT, Robert Haas <robertmhaas@gmail.com> wrote:
>On Thu, Jul 19, 2018 at 3:42 PM, Andres Freund <andres@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.
My point is that we could just make HTSV treat them as recently dead, without incurring the issues of the bug you
referenced.
Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
