Re: Freeze avoidance of very large table.

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>, Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Greg Stark <stark(at)mit(dot)edu>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Subject: Re: Freeze avoidance of very large table.
Date: 2015-10-21 18:24:45
Message-ID: 5627D86D.6070903@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 10/21/15 8:11 AM, Andres Freund wrote:
> Meh. Adding complexity definitely needs to be weighed against the
> benefits. As pointed out e.g. by all the multixact issues you mentioned
> upthread. In this case your argument for changing the name doesn't seem
> to hold much water.

ISTM VISIBILITY_MAP_FROZEN_BIT_CAT_VER shold be defined in catversion.h
instead of pg_upgrade.h though, to ensure it's correctly updated when
this gets committed though.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2015-10-21 18:26:19 Re: BUG #13694: Row Level Security by-passed with CREATEUSER permission
Previous Message Tom Lane 2015-10-21 18:17:44 Re: BUG #13694: Row Level Security by-passed with CREATEUSER permission