| From: | tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Vacuum o/p with (full 1, parallel 0) option throwing an error |
| Date: | 2020-04-08 12:22:12 |
| Message-ID: | 58c8d171-e665-6fa3-a9d3-d9423b694dae@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토SQL : Postg토토SQL |
Hi,
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.
--
regards,tushar
EnterpriseDB https://www.enterprisedb.com/
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2020-04-08 12:23:42 | Re: Thoughts on "killed tuples" index hint bits support on standby |
| Previous Message | Peter Eisentraut | 2020-04-08 12:21:19 | Re: adding partitioned tables to publications |