Re: Freeze avoidance of very large table. - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: Freeze avoidance of very large table.
Date
Msg-id CAB7nPqTxuOfNbh-kPariJOmCTfdXdhDPR5uSOiS7kdNN+K1FWA@mail.gmail.com
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Andres Freund <andres@anarazel.de>)
Responses Re: Freeze avoidance of very large table.  (andres@anarazel.de (Andres Freund))
List pgsql-hackers
On Thu, Dec 17, 2015 at 4:10 PM, Andres Freund <andres@anarazel.de> wrote:
> On 2015-12-17 15:56:35 +0900, Michael Paquier wrote:
>> On Thu, Dec 17, 2015 at 3:44 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> > For me, rewriting the visibility map is a new data loss bug waiting to
>> > happen. I am worried that the group is not taking seriously the potential
>> > for catastrophe here.
>>
>> FWIW, I'm following this line and merging the vm file into a single
>> unit looks like a ticking bomb.
>
> And what are those risks?

Incorrect vm file rewrite after a pg_upgrade run.
-- 
Michael



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Refactoring speculative insertion with unique indexes a little
Next
From: andres@anarazel.de (Andres Freund)
Date:
Subject: Re: Freeze avoidance of very large table.