Re: [PROPOSAL] VACUUM Progress Checker.

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "Syed, Rahila" <Rahila(dot)Syed(at)nttdata(dot)com>, Thom Brown <thom(at)linux(dot)com>, "PostgreSQL-development (pgsql-hackers(at)postgresql(dot)org)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PROPOSAL] VACUUM Progress Checker.
Date: 2015-09-29 00:36:52
Message-ID: CAD21AoA+vrA1C6rYvF-v2L0Fyzu0BS_w6cg=zHf7UvXE0=QxPw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Sep 28, 2015 at 11:03 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Sep 24, 2015 at 8:37 AM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>> When we run "VACUUM;", the all tables of current database will be vacuumed.
>> So pg_stat_vacuum_progress should have these oid in order to show
>> which table is vacuumed now.
>
> Hmm, I would tend to instead show the schema & table name, like "foo"."bar".
>

Yes, it looks better.

Regards,

--
Masahiko Sawada

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2015-09-29 01:49:12 Re: Rework the way multixact truncations work
Previous Message Kouhei Kaigai 2015-09-29 00:31:11 Re: CustomScan support on readfuncs.c