Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1tMZug-0056QK-C3
	for pgsql-admin@arkaria.postgresql.org; Sat, 14 Dec 2024 21:43:02 +0000
Received: from localhost ([127.0.0.1] helo=malur.postgresql.org)
	by malur.postgresql.org with esmtp (Exim 4.94.2)
	(envelope-from <pgsql-admin-owner+archive@lists.postgresql.org>)
	id 1tMZud-0079QI-0m
	for pgsql-admin@arkaria.postgresql.org; Sat, 14 Dec 2024 21:43:00 +0000
Received: from makus.postgresql.org ([2001:4800:3e1:1::229])
	by malur.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tMZuc-0079QA-LO
	for pgsql-admin@lists.postgresql.org; Sat, 14 Dec 2024 21:42:59 +0000
Received: from sss.pgh.pa.us ([68.162.161.243])
	by makus.postgresql.org with esmtps  (TLS1.3) tls
 TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
	(Exim 4.94.2)
	(envelope-from <tgl@sss.pgh.pa.us>)
	id 1tMZuX-002r9D-Lf
	for pgsql-admin@postgresql.org; Sat, 14 Dec 2024 21:42:58 +0000
Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 4BELgqkH1472807;
	Sat, 14 Dec 2024 16:42:52 -0500
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ron Johnson <ronljohnsonjr@gmail.com>
cc: pgsql-admin <pgsql-admin@postgresql.org>
Subject: Re: Why might it take so long to start up a cleanly-stopped instance?
In-reply-to: 
 <CANzqJaAXfBAirx+Pf3xQXfgaGVyuyJ06BbOAUBRW3jJe+onu4w@mail.gmail.com>
References: 
 <CANzqJaAXfBAirx+Pf3xQXfgaGVyuyJ06BbOAUBRW3jJe+onu4w@mail.gmail.com>
Comments: In-reply-to Ron Johnson <ronljohnsonjr@gmail.com>
	message dated "Sat, 14 Dec 2024 13:28:55 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1472805.1734212572.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Sat, 14 Dec 2024 16:42:52 -0500
Message-ID: <1472806.1734212572@sss.pgh.pa.us>
List-Id: <pgsql-admin.lists.postgresql.org>
List-Help: <https://lists.postgresql.org/manage/>
List-Subscribe: <https://lists.postgresql.org/manage/>
List-Post: <mailto:pgsql-admin@lists.postgresql.org>
List-Owner: <mailto:pgsql-admin-owner@lists.postgresql.org>
List-Archive: <https://www.postgresql.org/list/pgsql-admin>
Archived-At: 
 <https://www.postgresql.org/message-id/1472806.1734212572%40sss.pgh.pa.us>
Precedence: bulk

Ron Johnson <ronljohnsonjr@gmail.com> writes:
> $ pg_ctl stop -wt9999 && pg_ctl start -wt9999
> waiting for server to shut down........... done
> server stopped
> waiting for server to
> start...................................................................=
..........................................................................=
..........................................................................=
..........2024-12-14
> 13:21:10.820 EST            24567            00000   LOG:  00000:
> redirecting log output to logging collector process
> 2024-12-14 13:21:10.820 EST            24567            00000   HINT:
>  Future log output will appear in directory "/var/log/postgresql".
> 2024-12-14 13:21:10.820 EST            24567            00000   LOCATION=
:
>  SysLogger_Start, syslogger.c:674
> . done
> server started

That's quite odd: the delay evidently happens before SysloggerStart,
which is done mighty early.  Perhaps strace'ing the start would yield
insight.

			regards, tom lane