Re: [COMMITTERS] pgsql: Allow vacuums to report oldestxmin - Mailing list pgsql-committers

From Fujii Masao
Subject Re: [COMMITTERS] pgsql: Allow vacuums to report oldestxmin
Date
Msg-id CAHGQGwHWWT6N-65DZijHHjCUbxEPDyUP7L5x0ZT6b3=d4d7V7w@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Allow vacuums to report oldestxmin  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-committers
On Mon, Mar 6, 2017 at 9:37 PM, Masahiko Sawada <sawada.mshk@gmail.com> wrote:
> On Fri, Mar 3, 2017 at 10:50 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
>> Allow vacuums to report oldestxmin
>>
>> Allow VACUUM and Autovacuum to report the oldestxmin value they
>> used while cleaning tables, helping to make better sense out of
>> the other statistics we report in various cases.
>>
>> Branch
>> ------
>> master
>>
>> Details
>> -------
>> http://git.postgresql.org/pg/commitdiff/9eb344faf54a849898d9be012ddfa8204cfeb57c
>>
>> Modified Files
>> --------------
>> src/backend/commands/vacuumlazy.c | 9 +++++----
>> 1 file changed, 5 insertions(+), 4 deletions(-)
>>
>>
>
> Should we change the example in vacuum.sgml file as well? Attached patch.

"tuples" in the above should be "row versions"?
We should review not only this line but also all the lines in the example
of VERBOSE output, I think.

Regards,

--
Fujii Masao


pgsql-committers by date:

Previous
From: Stephen Frost
Date:
Subject: Re: pgsql: Add COMMENT and SECURITY LABEL support forpublications and subs
Next
From: Masahiko Sawada
Date:
Subject: Re: [COMMITTERS] pgsql: Allow vacuums to report oldestxmin