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

From: "Bossart, Nathan" <bossartn(at)amazon(dot)com>
To: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: [Proposal] Allow users to specify multiple tables in VACUUM commands
Date: 2017-05-17 22:38:10
Message-ID: AE4EAD7D-6C7D-404C-A95E-032EACE21FD4@amazon.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

I’ve attached a v4 of the patch.

Changes:
- Early in vacuum(…), emit an ERROR if any specified columns do not exist.
- Emit a WARNING and skip any specified tables or columns that disappear before they are actually processed.
- Small additions to the VACUUM regression test.
- Rebased with master.

Nathan

Attachment Content-Type Size
vacuum_multiple_tables_v4.patch application/octet-stream 29.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2017-05-17 23:01:38 Re: PG10 pgindent run
Previous Message Thomas Munro 2017-05-17 22:13:34 Re: transition table behavior with inheritance appears broken (was: Declarative partitioning - another take)