Hi, On 2022-11-14 14:42:16 -0800, Peter Geoghegan wrote: > What does this have to tell us, if anything, about the implications > for code on HEAD?
Nothing really test I sent (*) - I wanted to advance the discussion about the patch being wrong as-is in a concrete way. This logic was one of my main complaints in https://postgr.es/m/20221109220803.t25sosmfvkeglhy4%40awork3.anarazel.de and you went in a very different direction in your reply. Hence a test showcasing the issue. Note that neither of my complaints around FrozenTransactionId in that email actually require that HOT is involved. The code in the patch doesn't differentiate between hot and not-hot until later. > I don't see any connection between this problem and the possibility of a > live bug on HEAD involving freezing later tuple versions in a HOT chain, > leaving earlier non-frozen versions behind to break HOT chain traversal > code. Should I have noticed such a connection? No. Greetings, Andres Freund (*) the commented out test perhaps is an argument for expanding the comment nd "We will advance past RECENTLY_DEAD tuples just in case there's a DEAD after them;" in heap_prune_chain()
