Jonathan Katz <jonathan.k...@excoventures.com> writes:
> I see this one
> > Fix potential data corruption when freezing a tuple whose XMAX is a
> multixact with exactly one still-interesting member
> But I’m unsure how prevalent it is and if it should be highlighted.
I'm not sure about that either. I do not think anyone did the legwork
to determine the exact consequences of that bug, or the probability of
someone hitting it in the field. But I think the latter must be really
low, because we haven't heard any field reports that seem to match up.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
