| From: | Christoph Berg <myon(at)debian(dot)org> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Pg Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: pg_utility ? |
| Date: | 2025-11-19 11:52:55 |
| Message-ID: | aR2vl0-m50MCA_VQ@msg.df7cb.de |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Re: Álvaro Herrera
> Christoph, can you please confirm that this is approximately what you
> had in mind? Other names are of course possible.
Sorry for the late reply, the mail got lost in my inbox.
Yes that's what I had in mind.
> I didn't immediately love this idea, but I'm not totally opposed to it
> either, and perhaps it makes things better rather than adding yet
> another very narrowly-focused tool. Also, pg_ctl already kinda has a
> somewhat similar facet with its "pg_ctl init" mode.
I would keep the server and client bits separate, though, so not merge
these into pg_ctl.
I don't have an idea for the ideal name, perhaps only that it should
be short, and distinct from pg_ctl so people don't get confused. (So
not pg_cmd or pg_cli.)
Perhaps pg_util? ("pg" is taken by that classic pager thingy.)
Christoph
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dagfinn Ilmari Mannsåker | 2025-11-19 11:56:28 | Re: gen_guc_tables.pl: Validate required GUC fields before code generation |
| Previous Message | Fujii Masao | 2025-11-19 11:46:25 | Re: Exit walsender before confirming remote flush in logical replication |