From: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
---|---|
To: | Nitin Jadhav <nitinjadhavpostgres(at)gmail(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, Stephen Frost <sfrost(at)snowman(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: when the startup process doesn't (logging startup delays) |
Date: | 2021-08-03 13:10:09 |
Message-ID: | 20210803131008.GU12533@telsasoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Two issues that I saw:
The first syncfs message is not output, because it's before
InitStartupProgress() is called:
2021-08-03 07:53:02.176 CDT startup[9717] LOG: database system was interrupted; last known up at 2021-08-03 07:52:15 CDT
2021-08-03 07:53:02.733 CDT startup[9717] LOG: data directory sync (syncfs) complete after 0.55 s
2021-08-03 07:53:02.734 CDT startup[9717] LOG: database system was not properly shut down; automatic recovery in progress
FP exception when the GUC is set to 0:
2021-08-03 07:53:02.877 CDT postmaster[9715] LOG: startup process (PID 9717) was terminated by signal 8: Floating point exception
Probably due to mod zero operation.
This prevents the process from starting.
+ enable_timeout_after(LOG_STARTUP_PROGRESS_TIMEOUT,
+ (interval_in_ms - (elapsed_ms % interval_in_ms)));
--
Justin
From | Date | Subject | |
---|---|---|---|
Next Message | Tomas Vondra | 2021-08-03 13:33:28 | Re: slab allocator performance issues |
Previous Message | Erik Rijkers | 2021-08-03 13:02:43 | Re: [PATCH] proposal for regexp_count, regexp_instr, regexp_substr and regexp_replace |