Re: Draft release notes up for review

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jonathan Katz <jonathan(dot)katz(at)excoventures(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Draft release notes up for review
Date: 2017-08-05 21:37:33
Message-ID: 14454.1501969053@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jonathan Katz <jonathan(dot)katz(at)excoventures(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2017-08-05 22:16:14 Re: Draft release notes up for review
Previous Message Jonathan Katz 2017-08-05 21:09:32 Re: Draft release notes up for review