| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Ron Johnson <ronljohnsonjr(at)gmail(dot)com> |
| Cc: | pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Why might it take so long to start up a cleanly-stopped instance? |
| Date: | 2024-12-14 21:42:52 |
| Message-ID: | 1472806.1734212572@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Ron Johnson <ronljohnsonjr(at)gmail(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ron Johnson | 2024-12-15 07:39:05 | "a REINDEX operation on an index pg_upgrade'd from a previous release could potentially fail." |
| Previous Message | Ron Johnson | 2024-12-14 18:28:55 | Why might it take so long to start up a cleanly-stopped instance? |