| From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: [PATCH v2] Don't stop a `vacuumdb --all` on a connection failure |
| Date: | 2026-07-29 20:40:22 |
| Message-ID: | 6375DB48-9C5D-46F7-B306-3437C18D01D9@yesql.se |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> On 29 Jul 2026, at 18:25, Christophe Pettus <xof(at)thebuild(dot)com> wrote:
> There was no particular reason besides lack of ambition that reindexdb and clusterdb were not included. I've added them.
>
> Agreed with Daniel that a switch to control the new behavior makes sense (I hadn't through about the status code issue).
>
> Revised patch attached (I've kept the patch name and Subject: consistent for indexing purposes). It applies cleanly to 9fa2c1ebd17.
I've only skimmed the patch thus far, but in general this seems like a good
idea to me.
--
Daniel Gustafsson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2026-07-29 21:18:06 | Re: add list of major features to the v19 release notes |
| Previous Message | Daniel Gustafsson | 2026-07-29 20:31:34 | Re: pg_restore --format= option(without any value) should report an error as pg_dump is reporting an error |