Re: Count and log pages set all-frozen by vacuum

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Melanie Plageman <melanieplageman(at)gmail(dot)com>, Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com>, Alastair Turner <minion(at)decodable(dot)me>, Peter Geoghegan <pg(at)bowt(dot)ie>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>
Subject: Re: Count and log pages set all-frozen by vacuum
Date: 2024-11-27 17:01:41
Message-ID: CA+Tgmoab7Q6OVa_+RV_ic_ymEYB7RGwneS2djYKK8=b3dG4Vuw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Nov 26, 2024 at 8:38 PM Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
> > visibility map: 5 pages set all-visible, 4 pages set all-frozen.
>
> Which means that 5 pages were marked as only all-visible and 4 pages
> were marked as all-frozen (and possibly all-visible too). The total
> number of pages' whose VM status changed is the sum of these two
> numbers, 9 pages. We would have no idea how many total VM bits were
> set, though.

To me, the above output means 9 bits changed, 5 of which were
all-visible bits and 4 of which were all-frozen bits. It doesn't say
whether they were the same pages or not (although we might be able to
infer that based on only 3 of the 4 states being valid).

If you want to count the number of pages that changed state, then I
think the message wording needs to be different, but personally I
think counting the number of flipped bits of each type seems easier to
understand.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2024-11-27 17:01:50 Re: Statistics Import and Export
Previous Message Bruce Momjian 2024-11-27 17:00:21 Re: Statistics Import and Export