| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, 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-09 01:36:54 |
| Message-ID: | 20200409013654.GM1606@paquier.xyz |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Apr 08, 2020 at 01:38:54PM -0500, Justin Pryzby wrote:
> I think the behavior is correct, but the error message could be improved, like:
> |ERROR: cannot specify FULL with PARALLEL jobs
> or similar.
Perhaps "cannot use FULL and PARALLEL options together"? I think that
this patch needs tests in sql/vacuum.sql.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2020-04-09 01:45:50 | Re: Commitfest 2020-03 Now in Progress |
| Previous Message | Michael Paquier | 2020-04-09 01:25:46 | Re: Commitfest 2020-03 Now in Progress |