MIME-Version: 1.0
References: <CAPR5_5psNqCm1OQr5LL4v6z02Sh=2YHYUg8NY+3xMzfGHfKs+w@mail.gmail.com>
 <ea93ff28-4496-4e3d-a529-191582e02344@aklaver.com>
In-Reply-To: <ea93ff28-4496-4e3d-a529-191582e02344@aklaver.com>
From: Ron Johnson <ronljohnsonjr@gmail.com>
Date: Sat, 11 Oct 2025 22:56:31 -0400
Message-ID: <CANzqJaBOWpoBDSNsxO=+zna1DEAqUNct5wm=4vQsOXiPwY7x=Q@mail.gmail.com>
Subject: Re: Option on `postgres` CLI to shutdown when there are no more
 active connections?
To: pgsql-general <pgsql-general@postgresql.org>
Content-Type: multipart/alternative; boundary="000000000000f067760640ed4c6d"
Archived-At: <https://www.postgresql.org/message-id/CANzqJaBOWpoBDSNsxO%3D%2Bzna1DEAqUNct5wm%3D4vQsOXiPwY7x%3DQ%40mail.gmail.com>
Precedence: bulk

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

On Sat, Oct 11, 2025 at 7:11=E2=80=AFPM Adrian Klaver <adrian.klaver@aklave=
r.com>
wrote:

> On 10/8/25 12:39, David Barsky wrote:
> > Hiya folks,
> >
> > I'm a bit of a newcomer when it comes to PostgreSQL, so I apologize if
> > this is
> > the wrong mailing list. Anyways, my two questions:
> >
> > 1. Is there any interest in adding a command line option to the
> > `postgres` CLI
> >     that shuts down the PostgreSQL instance once (and optionally cleans
> > up the
> >     data directory) once all connections have disconnected?
>
> https://www.postgresql.org/docs/current/app-pg-ctl.html
>
> "
> stop mode shuts down the server that is running in the specified data
> directory. Three different shutdown methods can be selected with the -m
> option. =E2=80=9CSmart=E2=80=9D mode disallows new connections, then wait=
s for all
> existing clients to disconnect. If the server is in hot standby,
> recovery and streaming replication will be terminated once all clients
> have disconnected. =E2=80=9CFast=E2=80=9D mode (the default) does not wai=
t for clients
> to disconnect. All active transactions are rolled back and clients are
> forcibly disconnected, then the server is shut down. =E2=80=9CImmediate=
=E2=80=9D mode
> will abort all server processes immediately, without a clean shutdown.
> This choice will lead to a crash-recovery cycle during the next server
> start.
> "
>

I think OP is looking for AUTO_CLOSE, like SQL Server (and Rdb/VMS before
it).  Its only real utility is OP's use-case: a Windows desktop running
local testing.

We in the shell scripting daemon world don't think like that.

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

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

<div dir=3D"ltr"><div dir=3D"ltr">On Sat, Oct 11, 2025 at 7:11=E2=80=AFPM A=
drian Klaver &lt;<a href=3D"mailto:adrian.klaver@aklaver.com">adrian.klaver=
@aklaver.com</a>&gt; wrote:</div><div class=3D"gmail_quote gmail_quote_cont=
ainer"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">On 10/8/25 12:39, =
David Barsky wrote:<br>
&gt; Hiya folks,<br>
&gt; <br>
&gt; I&#39;m a bit of a newcomer when it comes to PostgreSQL, so I apologiz=
e if <br>
&gt; this is<br>
&gt; the wrong mailing list. Anyways, my two questions:<br>
&gt; <br>
&gt; 1. Is there any interest in adding a command line option to the <br>
&gt; `postgres` CLI<br>
&gt;=C2=A0 =C2=A0 =C2=A0that shuts down the PostgreSQL instance once (and o=
ptionally cleans <br>
&gt; up the<br>
&gt;=C2=A0 =C2=A0 =C2=A0data directory) once all connections have disconnec=
ted?<br>
<br>
<a href=3D"https://www.postgresql.org/docs/current/app-pg-ctl.html" rel=3D"=
noreferrer" target=3D"_blank">https://www.postgresql.org/docs/current/app-p=
g-ctl.html</a><br>
<br>
&quot;<br>
stop mode shuts down the server that is running in the specified data <br>
directory. Three different shutdown methods can be selected with the -m <br=
>
option. =E2=80=9CSmart=E2=80=9D mode disallows new connections, then waits =
for all <br>
existing clients to disconnect. If the server is in hot standby, <br>
recovery and streaming replication will be terminated once all clients <br>
have disconnected. =E2=80=9CFast=E2=80=9D mode (the default) does not wait =
for clients <br>
to disconnect. All active transactions are rolled back and clients are <br>
forcibly disconnected, then the server is shut down. =E2=80=9CImmediate=E2=
=80=9D mode <br>
will abort all server processes immediately, without a clean shutdown. <br>
This choice will lead to a crash-recovery cycle during the next server <br>
start.<br>
&quot;<br></blockquote><div><br></div><div>I think OP is looking for AUTO_C=
LOSE, like SQL Server (and Rdb/VMS before it).=C2=A0 Its only real utility =
is OP&#39;s use-case: a Windows desktop=C2=A0running local testing.</div><d=
iv><br></div><div>We in the shell scripting daemon world don&#39;t think li=
ke that.</div><div><br></div></div><span class=3D"gmail_signature_prefix">-=
- </span><br><div dir=3D"ltr" class=3D"gmail_signature"><div dir=3D"ltr">De=
ath to &lt;Redacted&gt;, and butter sauce.<div>Don&#39;t boil me, I&#39;m s=
till alive.<br><div><div>&lt;Redacted&gt; lobster!</div></div></div></div><=
/div></div>

--000000000000f067760640ed4c6d--