Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
От | Masahiko Sawada |
---|---|
Тема | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
Дата | |
Msg-id | CA+fd4k5-Y8ed3ui1fT1N0Xd7aN4JnSd45=w3=v5Rs4z7wZDj6A@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On Fri, 10 Apr 2020 at 14:04, Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Thu, Apr 9, 2020 at 2:03 PM Justin Pryzby <pryzby@telsasoft.com> wrote: > > > > On Thu, Apr 09, 2020 at 05:07:48PM +0900, Masahiko Sawada wrote: > > > Yes but the difference is that we cannot disable PARSER or COPY by > > > specifying options whereas we can do something like "VACUUM (FULL > > > false) tbl" to disable FULL option. I might be misunderstanding the > > > meaning of "specify" though. > > > > You have it right. > > > > We should fix the behavior, but change the error message for consistency with > > that change, like so. > > > > Okay, but I think the error message suggested by Robert "ERROR: VACUUM > FULL cannot be performed in parallel" sounds better than what you have > proposed. What do you think? I totally agree. Regards, -- Masahiko Sawada http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: