| From: | Christophe Pettus <xof(at)thebuild(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Neil Chen <carpenter(dot)nail(dot)cz(at)gmail(dot)com> |
| Cc: | 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 16:25:47 |
| Message-ID: | E9C488DD-C82E-44AC-BE07-376F734B463E@thebuild.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Thank you, Neil and Daniel!
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.
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-vacuumdb-skip-unconnectable-databases,patch | application/octet-stream | 28.6 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tristan Partin | 2026-07-29 16:25:56 | Re: Add pg_stat_kind_info system view |
| Previous Message | Andrey Rachitskiy | 2026-07-29 16:13:04 | Re: Build warning with meson and dtrace on Fedora 43 |