| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Wrong return code in vacuumdb when multiple jobs are used |
| Date: | 2019-05-04 12:28:48 |
| Message-ID: | CAOBaU_aGRG_cFom+kjHxdaC_dMj2mmb7k-dh1y=Fs-4TTUR_WQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, May 4, 2019 at 2:17 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> On Sat, May 04, 2019 at 04:34:59PM +0530, Amit Kapila wrote:
> > The fix looks good to me as well.
>
> We are very close to the next minor release, so it may not be that
> wise to commit a fix for that issue now as we should have a couple of
> clean buildfarm clean runs.
Agreed.
> Are there any objections to wait after
> the release? Or would folks prefer if this is fixed before the
> release?
No objection from me. It's been broken since introduction in 9.5 and
has never been noticed since, so it can wait until next release.
Should I register the patch in the next commitfest to keep track of
it?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2019-05-04 12:41:52 | Re: Wrong return code in vacuumdb when multiple jobs are used |
| Previous Message | Michael Paquier | 2019-05-04 12:17:53 | Re: Wrong return code in vacuumdb when multiple jobs are used |