Re: Freeze avoidance of very large table.

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
Cc: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Petr Jelinek <petr(at)2ndquadrant(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, 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-07-02 16:23:04
Message-ID: CANP8+j+=rMz8_-zAaJv_cKTHHAaye7s+SpMpVDVXbqVGDb-KEA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2 July 2015 at 16:30, Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com> wrote:

> Also, the flags of each heap page header might be set PD_ALL_FROZEN,
> as well as all-visible
>

Is it possible to have VM bits set to frozen but not visible?

The description makes those two states sound independent of each other.

Are they? Or not? Do we test for an impossible state?

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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2015-07-02 17:03:01 Re: Doubt about AccessExclusiveLock in ALTER TABLE .. SET ( .. );
Previous Message Heikki Linnakangas 2015-07-02 16:22:51 Re: Fix autoconf deprecation warnings