Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
От | Mahendra Singh Thalor |
---|---|
Тема | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
Дата | |
Msg-id | CAKYtNAqzJ8rTh9Mb+2XdsH0dyZb2MS_XH-w8vz3i347etnaFSQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: Vacuum o/p with (full 1, parallel 0) option throwing an error
|
Список | pgsql-hackers |
On Wed, 8 Apr 2020 at 17:59, Robert Haas <robertmhaas@gmail.com> wrote: > > On Wed, Apr 8, 2020 at 8:22 AM tushar <tushar.ahuja@enterprisedb.com> wrote: > > I just came across this scenario where - vaccum o/p with (full 1, > > parallel 0) option not working > > > > --working > > > > postgres=# vacuum (parallel 1, full 0 ) foo; > > VACUUM > > postgres=# > > > > --Not working > > > > postgres=# vacuum (full 1, parallel 0 ) foo; > > ERROR: cannot specify both FULL and PARALLEL options > > > > I think it should work. > > Uh, why? There's a clear error message which matches what you tried to do. > I think, Tushar point is that either we should allow both vacuum(parallel 0, full 1) and vacuum(parallel 1, full 0) or in the both cases, we should through error. -- Thanks and Regards Mahendra Singh Thalor EnterpriseDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: