| From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
|---|---|
| To: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Vacuum o/p with (full 1, parallel 0) option throwing an error |
| Date: | 2020-04-09 08:33:19 |
| Message-ID: | 20200409083319.GN2228@telsasoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Justin
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Allow-specifying-parallel-0-with-vacuum-full.patch | text/x-diff | 3.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dilip Kumar | 2020-04-09 09:10:17 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
| Previous Message | davinder singh | 2020-04-09 08:25:22 | Re: PG compilation error with Visual Studio 2015/2017/2019 |