Re: [HACKERS] [Proposal] Allow users to specify multiple tables in VACUUM commands
От | Tom Lane |
---|---|
Тема | Re: [HACKERS] [Proposal] Allow users to specify multiple tables in VACUUM commands |
Дата | |
Msg-id | 10905.1505955071@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands (Michael Paquier <michael.paquier@gmail.com>) |
Ответы |
Re: [HACKERS] [Proposal] Allow users to specify multiple tables inVACUUM commands
|
Список | pgsql-hackers |
Michael Paquier <michael.paquier@gmail.com> writes: > On Thu, Sep 21, 2017 at 9:08 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: >> Um ... so? With Nathan's proposed behavior, there are two cases depending >> on just when the unexpected schema change happens: >> 1. *None* of the work gets done. >> 2. The work before the troublesome relation gets done, and the work after >> doesn't. > You may be missing one which is closer to what autovacuum does: > 3) Issue a warning for the troublesome relation, and get the work done > a maximum. Well, we could certainly discuss whether the behavior on detecting a conflict ought to be "error" or "warning and continue". But I do not buy the value of "it might be one or the other depending on timing". regards, tom lane -- 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 по дате отправления: