From: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
Date: | 2020-04-08 14:24:49 |
Message-ID: | CAKYtNAqzJ8rTh9Mb+2XdsH0dyZb2MS_XH-w8vz3i347etnaFSQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, 8 Apr 2020 at 17:59, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>
> On Wed, Apr 8, 2020 at 8:22 AM tushar <tushar(dot)ahuja(at)enterprisedb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | David Steele | 2020-04-08 14:26:38 | Re: Verify true root on replicas with amcheck |
Previous Message | David Steele | 2020-04-08 14:24:19 | Re: Online checksums patch - once again |