From: Thorsten Glaser <tg@evolvis.org>
To: Telium Technical Support <support@telium.io>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_ctlcluster is not stopping cluster
Date: Sat, 8 Apr 2023 00:49:30 +0200 (CEST)
Message-ID: <1c1a4fe5-ffe3-5d8d-294c-e9c177decca@evolvis.org> (raw)
In-Reply-To: <010001875dd4ebe6-ba96b71f-2461-45da-ab24-0abf56f56f4f-000000@email.amazonses.com>
References: <010001875dd4ebe6-ba96b71f-2461-45da-ab24-0abf56f56f4f-000000@email.amazonses.com>
On Fri, 7 Apr 2023, Telium Technical Support wrote:
>Notice: extra pg_ctl/postgres options given, bypassing systemctl for stop
>it might be 13. Coincidentally, there is a postmaster.pid file in a
>directory OTHER than the data directory:
>
>/var/lib/postgresql/15/main/postmaster.pid
>
>(and notice the 15). Is this a clue?
Maybe the pidfile is written into the cluster version-based directory
instead of the data directory. Best figure out what exactly writes the
pidfile, whether systemd is used for starting (which would of course be
a prime suspect as it says it’s explicitly not used for stopping), etc.
Maybe this is indeed a bug in whatever determines the pidfile path,
perhaps not; is it supposed to live within the data directory?
bye,
//mirabilos
--
15:41⎜<Lo-lan-do:#fusionforge> Somebody write a testsuite for helloworld :-)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tg@evolvis.org, support@telium.io
Subject: Re: pg_ctlcluster is not stopping cluster
In-Reply-To: <1c1a4fe5-ffe3-5d8d-294c-e9c177decca@evolvis.org>
References: <010001875dd4ebe6-ba96b71f-2461-45da-ab24-0abf56f56f4f-000000@email.amazonses.com> <1c1a4fe5-ffe3-5d8d-294c-e9c177decca@evolvis.org>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox