Re: [Proposal] Allow users to specify multiple tables in VACUUM commands

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, "Masahiko Sawada" <sawada(dot)mshk(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Subject: Re: [Proposal] Allow users to specify multiple tables in VACUUM commands
Date: 2017-10-02 04:43:39
Message-ID: E99FB3A9-CFAB-4EA3-8272-C83DF20E4301@amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 9/29/17, 9:33 AM, "Bossart, Nathan" <bossartn(at)amazon(dot)com> wrote:
> Here's a version without the logging changes in vacuum_rel() and
> analyze_rel(). I’ll look into submitting those in the next commitfest.

Since get_rel_oids() was altered in 19de0ab2, here is a new version of
the patch.

Nathan

Attachment Content-Type Size
vacuum_multiple_tables_v25.patch application/octet-stream 29.0 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2017-10-02 06:13:11 Re: [Proposal] Allow users to specify multiple tables in VACUUM commands
Previous Message Kyotaro HORIGUCHI 2017-10-02 03:44:22 Re: Walsender timeouts and large transactions