pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jerry Sievers <gsievers19@comcast.net>
To: Thorsten Glaser <tg@evolvis.org>
Cc: Telium Technical Support <support@telium.io>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: pg_ctlcluster is not stopping cluster
Date: Fri, 07 Apr 2023 23:27:55 -0500
Message-ID: <m0bkjzxak4.fsf@comcast.net> (raw)
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>

Thorsten Glaser <tg@evolvis.org> writes:

> 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



Some distros in their wrapper foo, I believe including Debian use this
setting to put a PID file under /var/run/postgresql IIRC but YMMV...

external_pid_file (string)

 Specifies the name of an additional process-ID (PID) file that the
 server should create for use by server administration programs. This
 parameter can only be set at server start.


> 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





view thread (10+ messages)

Message-ID: <m0bkjzxak4.fsf@comcast.net>
Permalink:  ../m0bkjzxak4.fsf@comcast.net/
Also on:    postgresql.org/message-id/m0bkjzxak4.fsf@comcast.net

 · 

reply

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: gsievers19@comcast.net, tg@evolvis.org, support@telium.io
  Subject: Re: pg_ctlcluster is not stopping cluster
  In-Reply-To: <m0bkjzxak4.fsf@comcast.net>
  References: <010001875dd4ebe6-ba96b71f-2461-45da-ab24-0abf56f56f4f-000000@email.amazonses.com> <1c1a4fe5-ffe3-5d8d-294c-e9c177decca@evolvis.org> <m0bkjzxak4.fsf@comcast.net>

* 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