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

From Sawada Masahiko
Subject Re: Freeze avoidance of very large table.
Date
Msg-id CAD21AoBFnrp_Q-n8Xyg77OMDFDybFNd+4uq6ysAVHgVq+vcpKQ@mail.gmail.com
Whole thread Raw
In response to Re: Freeze avoidance of very large table.  (Sawada Masahiko <sawada.mshk@gmail.com>)
List pgsql-hackers
On Fri, Jul 3, 2015 at 5:25 PM, Sawada Masahiko <sawada.mshk@gmail.com> wrote:
> On Fri, Jul 3, 2015 at 1:23 AM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> On 2 July 2015 at 16:30, Sawada Masahiko <sawada.mshk@gmail.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?
>>
>
> It's impossible to have VM bits set to frozen but not visible.
> These bit are controlled independently. But eventually, when
> all-frozen bit is set, all-visible is also set.

Attached latest version including some bug fix.
Please review it.

Regards,

--
Sawada Masahiko

Attachment

pgsql-hackers by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: dblink: add polymorphic functions.
Next
From: Tom Lane
Date:
Subject: Re: WAL logging problem in 9.4.3?