| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Sabino Mullane <htamfids(at)gmail(dot)com> |
| Cc: | David Barsky <me(at)davidbarsky(dot)com>, Dominique Devienne <ddevienne(at)gmail(dot)com>, Ron Johnson <ronljohnsonjr(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Option on `postgres` CLI to shutdown when there are no more active connections? |
| Date: | 2025-10-16 22:22:07 |
| Message-ID: | 1570124.1760653327@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Greg Sabino Mullane <htamfids(at)gmail(dot)com> writes:
> On Mon, Oct 13, 2025 at 3:19 PM David Barsky <me(at)davidbarsky(dot)com> wrote:
>> Anyways, I'll try to get at what motivated this whole discussion: would
>> there be community opposition to adding a CLI flag that'd exit/shutdown all
>> Postgres processes once all pending connections close?
> I don't know about opposition, per se, but the onus is on you to provide a
> strong use case not already covered by existing tools.
In particular, it's not terribly clear why the existing "smart"
shutdown mode isn't sufficient.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2025-10-17 04:49:06 | Re: Enquiry about TDE with PgSQL |
| Previous Message | Greg Sabino Mullane | 2025-10-16 22:18:57 | Re: Option on `postgres` CLI to shutdown when there are no more active connections? |