| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Reviewing freeze map code |
| Date: | 2016-05-02 21:48:18 |
| Message-ID: | 20160502214818.psk3lmgyihk6gr3k@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
The freeze map changes, besides being very important, seem to be one of
the patches with a high risk profile in 9.6. Robert had asked whether
I'd take a look. I thought it'd be a good idea to review that while
running tests for
http://www.postgresql.org/message-id/CAMkU=1w85Dqt766AUrCnyqCXfZ+rsk1witAc_=v5+Pce93Sftw@mail.gmail.com
For starters, I'm just going through the commits. It seems the relevant
pieces are:
a892234 Change the format of the VM fork to add a second bit per page.
77a1d1e Department of second thoughts: remove PD_ALL_FROZEN.
fd31cd2 Don't vacuum all-frozen pages.
7087166 pg_upgrade: Convert old visibility map format to new format.
ba0a198 Add pg_visibility contrib module.
did I miss anything important?
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Ignatov | 2016-05-02 21:56:04 | Re: Is pg_control file crashsafe? |
| Previous Message | Tom Lane | 2016-05-02 21:23:58 | Re: pg_upgrade and toasted pg_largeobject |