Re: [HACKERS] free space map and visibility map - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] free space map and visibility map
Date
Msg-id CA+TgmoaqYk2LFDNDdpPVU2AbuyMOAh2Q6nSTxmChvOTqoQ_s1g@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] free space map and visibility map  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: [HACKERS] free space map and visibility map  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On Sat, Mar 18, 2017 at 5:42 PM, Jeff Janes <jeff.janes@gmail.com> wrote:
> Isn't HEAP2_CLEAN only issued before an intended HOT update?  (Which then
> can't leave the block as all visible or all frozen).  I think the issue is
> here is HEAP2_VISIBLE or HEAP2_FREEZE_PAGE.  Am I reading this correctly,
> that neither of those ever update the FSM, regardless of FPI?

Yes, updates to the FSM are never logged.  Forcing replay of
HEAP2_FREEZE_PAGE to update the FSM might be a good idea.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: [HACKERS] Inadequate traces in TAP tests
Next
From: Stephen Frost
Date:
Subject: [HACKERS] Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and codecoverage