From: | Jonathan Katz <jonathan(dot)katz(at)excoventures(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Draft release notes up for review |
Date: | 2017-08-06 13:59:57 |
Message-ID: | 7CC6EB95-0F85-4B31-AF07-4154A24BB6F6@excoventures.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On Aug 5, 2017, at 5:37 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> 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.
OK, thanks for the clarification. I will follow-up once I have the draft ready for technical review.
Thanks,
Jonathan
From | Date | Subject | |
---|---|---|---|
Next Message | Jonathan Katz | 2017-08-06 15:14:21 | Draft for 2017-08-10 Release |
Previous Message | AP | 2017-08-06 06:32:29 | Re: pgsql 10: hash indexes testing |