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: 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>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
Subject: Re: [Proposal] Allow users to specify multiple tables in VACUUM commands
Date: 2017-09-12 15:31:37
Message-ID: BB1CFD19-5204-4752-A1A5-10C7CE175B21@amazon.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

Sorry for the spam. I am re-sending these patches with modified names so that
the apply order is obvious to the new automated testing framework (and to
everybody else).

Nathan

Attachment Content-Type Size
0002-error_on_duplicate_columns_in_analyze_v4.patch application/octet-stream 6.1 KB
0001-vacuum_multiple_tables_v17.patch application/octet-stream 34.3 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2017-09-12 15:36:00 Re: More efficient truncation of pg_stat_activity query strings
Previous Message Tom Lane 2017-09-12 15:30:33 Re: Automatic testing of patches in commit fest