Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
От | Bossart, Nathan |
---|---|
Тема | Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands |
Дата | |
Msg-id | 32C9AC7F-94A2-45E8-876F-9384641F6530@amazon.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] [Proposal] Allow users to specify multiple tables in VACUUM commands (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
|
Список | pgsql-hackers |
On 10/3/17, 5:59 PM, "Tom Lane" <tgl@sss.pgh.pa.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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
В списке pgsql-hackers по дате отправления: