Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
От | Amit Kapila |
---|---|
Тема | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
Дата | |
Msg-id | CAA4eK1Ku4X-RYcT+h=ngE8Yt6fMCD2rXpAvG0rh=j=PS+K0zmg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error (Justin Pryzby <pryzby@telsasoft.com>) |
Ответы |
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
Список | pgsql-hackers |
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? -- With Regards, Amit Kapila. EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: