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

From Simon Riggs
Subject Re: Freeze avoidance of very large table.
Date
Msg-id CANP8+jLWbhcYnEug1UtZSX91vYjLA4v_RR5S2aMBAYxr8UmevA@mail.gmail.com
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Freeze avoidance of very large table.  (Amit Kapila <amit.kapila16@gmail.com>)
Re: Freeze avoidance of very large table.  (Sawada Masahiko <sawada.mshk@gmail.com>)
List pgsql-hackers
On 6 July 2015 at 17:28, Simon Riggs <simon@2ndquadrant.com> wrote:

I think we need something for pg_upgrade to rewrite existing VMs. Otherwise a large read only database would suddenly require a massive revacuum after upgrade, which seems bad. That can wait for now until we all agree this patch is sound.
 
Since we need to rewrite the "vm" map, I think we should call the new map "vfm" 

That way we will be able to easily check whether the rewrite has been conducted on all relations.

Since the maps are just bits there is no other way to tell that a map has been rewritten

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: replication slot restart_lsn initialization
Next
From: Andres Freund
Date:
Subject: Re: patch : Allow toast tables to be moved to a different tablespace