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

From Andres Freund
Subject Re: Freeze avoidance of very large table.
Date
Msg-id 20151217071049.GJ23112@awork2.anarazel.de
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: Freeze avoidance of very large table.  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
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?

> We may really want a separate _vm file, like _vmf to track this new
> bit flag but this has already been mentioned largely upthread...

That'd double the overhead when those bits get unset.



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Freeze avoidance of very large table.
Next
From: Michael Paquier
Date:
Subject: Re: Refactoring speculative insertion with unique indexes a little