pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bossart, Nathan <bossartn@amazon.com>
To: Masahiko Sawada <sawada.mshk@gmail.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Subject: Re: New vacuum option to do only freezing
Date: Wed, 27 Feb 2019 17:45:47 +0000
Message-ID: <631670BB-CE95-40B5-9550-3C10417862FA@amazon.com> (raw)
In-Reply-To: <CAD21AoDBXAuR8xmY7D715=FSHUO4KWDDCy2hid1ZxsTf7pwyRQ@mail.gmail.com>
References: <0EA5A139-A127-416B-963F-6301F9F8B75D@amazon.com>
	<201902021604.zimvqvgmo672@alvherre.pgsql>
	<CAD21AoDH9wSJaA9BSm0Scbk4Dxyj66ZumOVuZnKBDdCHb4wvPg@mail.gmail.com>
	<A959EFE3-3858-4E82-9993-AE9A82785544@amazon.com>
	<6C4C0FC7-5E3A-44C0-90E3-492DAC1183F0@amazon.com>
	<CAD21AoDBXAuR8xmY7D715=FSHUO4KWDDCy2hid1ZxsTf7pwyRQ@mail.gmail.com>

On 2/27/19, 2:08 AM, "Masahiko Sawada" <sawada.mshk@gmail.com> wrote:
>> +       if (skip_index_vacuum)
>> +               appendStringInfo(&buf, ngettext("%.0f tuple is left as dead.\n",
>> +                                                                               "%.0f tuples are left as dead.\n",
>> +                                                                               nleft),
>> +                                                nleft);
>>
>> I think we could emit this metric for all cases, not only when
>> DISABLE_INDEX_CLEANUP is used.
>
> I think that tups_vacuumed shows total number of vacuumed tuples and
> is already shown in the log message. The 'nleft' counts the total
> number of recorded dead tuple but not counts tuples are removed during
> HOT-pruning. Is this a valuable for users in non-DISABLE_INDEX_CLEANUP
> case?

I think it is valuable.  When DISABLE_INDEX_CLEANUP is not used or it
is used for a relation with no indexes, it makes it clear that no
tuples were left marked as dead.  Also, it looks like all of the other
information here is provided regardless of the options used.  IMO it
is good to list all of the stats so that users have the full picture
of what VACUUM did.

Nathan



view thread (118+ messages)  latest in thread

Message-ID: <631670BB-CE95-40B5-9550-3C10417862FA@amazon.com>
Permalink:  ../631670BB-CE95-40B5-9550-3C10417862FA@amazon.com/
Also on:    postgresql.org/message-id/631670BB-CE95-40B5-9550-3C10417862FA@amazon.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bossartn@amazon.com, sawada.mshk@gmail.com, alvherre@2ndquadrant.com, robertmhaas@gmail.com
  Subject: Re: New vacuum option to do only freezing
  In-Reply-To: <631670BB-CE95-40B5-9550-3C10417862FA@amazon.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox