Re: DISABLE_PAGE_SKIPPING option for vacuumdb

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: DISABLE_PAGE_SKIPPING option for vacuumdb
Date: 2016-09-14 01:10:22
Message-ID: CAD21AoB+9d9y5snE4sJEByJWCVQzsXrCtVj9nXFUm9e7iVpuMg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Sep 14, 2016 at 2:17 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Sep 8, 2016 at 1:32 PM, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> wrote:
>> Attached patch add --disable-page-skipping option to vacuumed command for 9.6.
>> If by any chance the freeze map causes the serious data corruption bug
>> then the user will want to run pg_check_visible() and vacuum with
>> DISABLE_PAGE_SKIPPING option to the multiple tables having problem.
>> In this case, I think that this option for vacuumdb would be convenient.
>>
>> Please give me feedback.
>
> I think this isn't really necessary.
>

Thank you for comment.

Okay, I thought it would be useful for user who want to vacuum with
disable_page_skipping specified table but it's non-essential.
I pull it back. Thanks.

Regards,

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-09-14 01:42:47 Re: Event trigger and CREATE/ALTER ROLE/USER
Previous Message Kouhei Kaigai 2016-09-14 01:07:46 Re: PassDownLimitBound for ForeignScan/CustomScan