Re: Reporting xmin from VACUUMs

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Reporting xmin from VACUUMs
Date: 2017-02-15 15:37:49
Message-ID: 7f7a2d88-4aeb-b17c-932d-a3fe499812fa@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Accidentally sent o--list.

On 2/14/17 12:57 PM, Jim Nasby wrote:
> On 2/13/17 12:36 AM, Masahiko Sawada wrote:
>>> 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.
>
> Yes, please. We now do that for pages skipped because we couldn't get
> the cleanup lock and skipping due to all-frozen is certainly more
> user-visible than that.
>
> ISTR previous discussion of allowing more stats files; if that happened
> I think having stats that were dedicated to (auto)vacuum would be very
> useful. That's clearly a lot more work though.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Christensen 2017-02-15 15:40:18 [PATCH] Teach Catalog.pm how many attributes there should be per DATA() line
Previous Message Kuntal Ghosh 2017-02-15 15:27:31 Re: Write Ahead Logging for Hash Indexes