Re: Reporting xmin from VACUUMs

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reporting xmin from VACUUMs
Date: 2017-02-13 06:36:00
Message-ID: CAD21AoAsibpq5Ro_wAzQzseftf26zpHDE84WP+yz9JL2Zes1fA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Feb 11, 2017 at 7:00 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Fri, Feb 10, 2017 at 3:30 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> We've added xmin info to pg_stat_activity and pg_stat_replication, but
>> VACUUM doesn't yet report which xmin value it used when it ran.
>>
>> Small patch to add this info to VACUUM output.

+1

> It seems sensible to me to do something like this. We already report
> a lot of other fine details, so what's one more? And it could be
> useful.

Also, I've been proposing to report the number of skipped the frozen
pages even in manual vacuum verbose log.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Masahiko Sawada 2017-02-13 07:05:23 Re: DROP SUBSCRIPTION and ROLLBACK
Previous Message Michael Paquier 2017-02-13 05:59:41 Re: contrib modules and relkind check