| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: free space map and visibility map |
| Date: | 2017-03-20 14:28:30 |
| Message-ID: | CA+TgmoaqYk2LFDNDdpPVU2AbuyMOAh2Q6nSTxmChvOTqoQ_s1g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Mar 18, 2017 at 5:42 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2017-03-20 14:35:15 | Re: [COMMITTERS] pgsql: Improve pg_dump regression tests and code coverage |
| Previous Message | Andrew Dunstan | 2017-03-20 14:27:39 | Re: Inadequate traces in TAP tests |