| From: | "Bossart, Nathan" <bossartn(at)amazon(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, "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-04 00:52:52 |
| Message-ID: | 32C9AC7F-94A2-45E8-876F-9384641F6530@amazon.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 10/3/17, 5:59 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I thought it would be a good idea to get this done before walking away
> from the commitfest and letting all this info get swapped out of my
> head. So I've reviewed and pushed this.
Thanks!
> I took out most of the infrastructure you'd put in for constructing
> RangeVars for tables not explicitly named on the command line. It
> was buggy (eg you can't assume a relcache entry will stick around)
> and I don't believe it's necessary. I don't think that warnings
> should be issued for any tables not explicitly named.
>
> In any case, though, the extent to which we should add more warning
> or log output seems like a fit topic for a new thread and a separate
> patch. Let's call this one done.
I'll look into submitting that to the next commitfest.
Nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-10-04 00:54:24 | Re: [Proposal] Allow users to specify multiple tables in VACUUM commands |
| Previous Message | Michael Paquier | 2017-10-04 00:15:44 | Re: [COMMITTERS] pgsql: Fix freezing of a dead HOT-updated tuple |