Re: Option on `postgres` CLI to shutdown when there are no more active connections?

From: Ron Johnson <ronljohnsonjr(at)gmail(dot)com>
To: "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-13 20:27:17
Message-ID: CANzqJaBepwWOdD3dOJPMx8KdHaA3xMk8NA9ST5oCK2HUoyqvig@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Oct 13, 2025 at 3:19 PM David Barsky <me(at)davidbarsky(dot)com> wrote:
[snip]

> 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? E.g., something similar to
> SQL
> Server's `auto_close` in the vein of `postgres
> -c "auto_close_after=100"` or `pg-ctl start --exit-mode=smart`?
>

If testing is all scripted, then why not put "pg_ctl stop" at the end of
the script?

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tim Gerber 2025-10-13 20:36:46 Re: Database in another drive
Previous Message John McKown 2025-10-13 20:21:45 Re: Database in another drive