| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
| Cc: | 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 12:29:07 |
| Message-ID: | CA+TgmoY6JBix-20yS=EicJVHNAH44QnYGQhyR_c15dZi02KF-w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | legrand legrand | 2020-04-08 12:32:54 | Re: Planning counters in pg_stat_statements (using pgss_store) |
| Previous Message | David Steele | 2020-04-08 12:27:39 | Re: WIP: WAL prefetch (another approach) |