| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com> |
| Subject: | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |
| Date: | 2017-08-24 22:45:40 |
| Message-ID: | CAB7nPqQM3TYOvcwatueLbFa4d6BrYohBYMNEmUFgfB8x-gkUYA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 24, 2017 at 11:28 PM, Bossart, Nathan <bossartn(at)amazon(dot)com> wrote:
> I should also note that the dedupe_relations(...) function needs another
> small fix for column lists. Since the lack of a column list means that we
> should ANALYZE all columns, a duplicate table name with an empty column
> list should effectively null out any other specified columns. For example,
> "ANALYZE table (a, b), table;" currently dedupes to the equivalent of
> "ANALYZE table (a, b);" when it should dedupe to "ANALYZE table;".
This makes me think that it could be a good idea to revisit this bit
in a separate patch. ANALYZE fails as well now when the same column is
defined multiple times with an incomprehensible error message.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-08-24 23:36:47 | Re: Update low-level backup documentation to match actual behavior |
| Previous Message | Andres Freund | 2017-08-24 22:23:02 | Re: MCXT_ALLOC_NO_OOM -> DSA_ALLOC_NO_OOM in dsa.c |