| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
| Cc: | David Steele <david(at)pgmasters(dot)net>, Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Ants Aasma <ants(dot)aasma(at)eesti(dot)ee>, Stephen Frost <sfrost(at)snowman(dot)net>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Reviewing freeze map code |
| Date: | 2016-05-18 13:45:03 |
| Message-ID: | CA+TgmoYE6wCKpoxnoJfqizpi-zTYHvjgN0YWR-hPzbZDWR_m6w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 18, 2016 at 9:42 AM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> It's not a bad thought, but I do think it might be a bit confusing.
>> My main priority for this new option is that people aren't tempted to
>> use it very often, and I think a name like "even_frozen_pages" is more
>> likely to accomplish that than just "frozen".
>
> freeze_all_pages?
No, that's what the existing FREEZE option does. This new option is
about unnecessarily vacuuming pages that don't need it. The
expectation is that vacuuming all-frozen pages will be a no-op.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2016-05-18 13:55:36 | Re: memory layouts for binary search in nbtree |
| Previous Message | Joshua D. Drake | 2016-05-18 13:42:37 | Re: Reviewing freeze map code |