| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | AKASH <akashbhujbal7051(at)gmail(dot)com> |
| Cc: | "submit(at)bugs(dot)debian(dot)org" <submit(at)bugs(dot)debian(dot)org>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Limitation in `pg_lsclusters` and `pg_dropcluster --stop` on Debian-based Systems |
| Date: | 2025-02-18 05:17:36 |
| Message-ID: | CAKFQuwbsvvC+vhGXB5mGYw-5F29W2B9wKGm8DYtxFW2oboDoOw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Monday, February 17, 2025, AKASH <akashbhujbal7051(at)gmail(dot)com> wrote:
> Package:`postgresql-common`
> Version:17
> Severity:Wishlist
> Reported by:Akash
> Date:18/02/2025
>
This isn’t a good place to publish such a wishlist since these tools are
not written by the core project developers for whom this list exists.
That said, neither 1 nor 2 seems all that likely to happen - either use the
tooling provided, and its conventions, or don’t.
The confirmation prompt for 3 I could see happening but it really isn’t how
Linux tooling is done generally, so I wouldn’t hold my breath. Especially
if you need someone to write the patch, not just approve it.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | AKASH | 2025-02-18 05:24:18 | Re: Limitation in `pg_lsclusters` and `pg_dropcluster --stop` on Debian-based Systems |
| Previous Message | AKASH | 2025-02-18 05:04:12 | Limitation in `pg_lsclusters` and `pg_dropcluster --stop` on Debian-based Systems |