MIME-Version: 1.0
References: <CAPR5_5psNqCm1OQr5LL4v6z02Sh=2YHYUg8NY+3xMzfGHfKs+w@mail.gmail.com>
 <ea93ff28-4496-4e3d-a529-191582e02344@aklaver.com> <CAPR5_5q2oCkw19rHb7oy-M0M0purWFM5Jc8ub5xDy_NdhUmRTw@mail.gmail.com>
 <73ff46d2-0bad-4a8d-9928-e494c2d5b0d1@gmail.com> <93702.1760321769@sss.pgh.pa.us>
 <CAFCRh-94eXetAjtCURs5F0JZQr=kso0rVgVSEmWiSD7wA6VcMw@mail.gmail.com>
 <CANzqJaDn_mVi4M0CbKnVNwK9RxYOneoCRmd_d69rbjBrwasuPQ@mail.gmail.com>
 <CAFCRh--P93bF0gpkdvg4MzMNqq5gK=4eWFkmBDR0xw9dmFVAPQ@mail.gmail.com>
 <233155.1760369829@sss.pgh.pa.us> <CAFCRh--_14QR1_=vZvKVZkcA_1LRO-pQd2p6BBRMreyAv2_z6w@mail.gmail.com>
 <CAPR5_5rRYkM9bO=KC_PY-Bj2Fw=t+maEYG+Am-UgaCHRTWyFsg@mail.gmail.com>
In-Reply-To: <CAPR5_5rRYkM9bO=KC_PY-Bj2Fw=t+maEYG+Am-UgaCHRTWyFsg@mail.gmail.com>
From: Greg Sabino Mullane <htamfids@gmail.com>
Date: Thu, 16 Oct 2025 18:18:57 -0400
Message-ID: <CAKAnmm+PUsTvXyyV3iWRDSS9qW2F0SBVXjqg_ZmpwpCy0xM4XQ@mail.gmail.com>
Subject: Re: Option on `postgres` CLI to shutdown when there are no more
 active connections?
To: David Barsky <me@davidbarsky.com>
Cc: Dominique Devienne <ddevienne@gmail.com>, Ron Johnson <ronljohnsonjr@gmail.com>, 
	"pgsql-generallists.postgresql.org" <pgsql-general@lists.postgresql.org>, Tom Lane <tgl@sss.pgh.pa.us>
Content-Type: multipart/alternative; boundary="000000000000dbeeb106414e022e"
Archived-At: <https://www.postgresql.org/message-id/CAKAnmm%2BPUsTvXyyV3iWRDSS9qW2F0SBVXjqg_ZmpwpCy0xM4XQ%40mail.gmail.com>
Precedence: bulk

--000000000000dbeeb106414e022e
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Oct 13, 2025 at 3:19=E2=80=AFPM David Barsky <me@davidbarsky.com> w=
rote:

> 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 a=
ll
> 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. I don't think that
bar has been met yet.

--
Cheers,
Greg

--
Crunchy Data - https://www.crunchydata.com
Enterprise Postgres Software Products & Tech Support

--000000000000dbeeb106414e022e
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Oct 13, 2025 at 3:19=E2=80=AFPM D=
avid Barsky &lt;<a href=3D"mailto:me@davidbarsky.com">me@davidbarsky.com</a=
>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_container"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr"=
>Anyways, I&#39;ll try to get at what motivated this whole discussion: woul=
d there be community opposition to adding a CLI flag that&#39;d exit/shutdo=
wn all Postgres</div><div dir=3D"ltr">processes once all pending connection=
s close?<br></div></div></blockquote><div><br></div><div>I don&#39;t know a=
bout opposition, per se, but the onus is on you to provide a strong use cas=
e not already covered by existing tools. I don&#39;t think that bar has bee=
n met yet.</div><div><br></div><div>--</div></div><div dir=3D"ltr" class=3D=
"gmail_signature"><div dir=3D"ltr"><div>Cheers,</div><div>Greg</div><div><b=
r></div><div>--</div><div>Crunchy Data - <a href=3D"https://www.crunchydata=
.com" target=3D"_blank">https://www.crunchydata.com</a></div><div>Enterpris=
e Postgres Software Products &amp; Tech Support</div><div><br></div></div><=
/div></div>

--000000000000dbeeb106414e022e--