Re: Why might it take so long to start up a cleanly-stopped instance? - Mailing list pgsql-admin

From Tom Lane
Subject Re: Why might it take so long to start up a cleanly-stopped instance?
Date
Msg-id 1472806.1734212572@sss.pgh.pa.us
Whole thread Raw
In response to Why might it take so long to start up a cleanly-stopped instance?  (Ron Johnson <ronljohnsonjr@gmail.com>)
List pgsql-admin
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



pgsql-admin by date:

Previous
From: Ron Johnson
Date:
Subject: Why might it take so long to start up a cleanly-stopped instance?
Next
From: Ron Johnson
Date:
Subject: "a REINDEX operation on an index pg_upgrade'd from a previous release could potentially fail."