pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Justin Pryzby <pryzby@telsasoft.com>
To: Nitin Jadhav <nitinjadhavpostgres@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Andres Freund <andres@anarazel.de>
Cc: Stephen Frost <sfrost@snowman.net>
Cc: Magnus Hagander <magnus@hagander.net>
Cc: Thomas Munro <thomas.munro@gmail.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: when the startup process doesn't (logging startup delays)
Date: Tue, 3 Aug 2021 08:10:09 -0500
Message-ID: <20210803131008.GU12533@telsasoft.com> (raw)
In-Reply-To: <CAMm1aWbg_jVm=dqzS1AZV4p6-u0Xfxcu0B9M0ptweG5gyzu-Mw@mail.gmail.com>
References: <20210726153023.GC23997@telsasoft.com>
	<CA+TgmoaP2wEFSktmCgwT9LXuz7Y99HNdUYshpk7qNFuQB98g6g@mail.gmail.com>
	<CAMm1aWZ29zwRu6n6U7QjJN21ZJQLyD5MVsVxoutWrJ06dYDq+A@mail.gmail.com>
	<CA+TgmobYNzfm8oBctUu9-Bt9YyuyOKGXEaPbuYi0LS9r3Ft2ug@mail.gmail.com>
	<CALj2ACXwH5FDv7LCsp59ru9+TTpD_=3CS2F3X-f0e-5Eb8+91Q@mail.gmail.com>
	<CA+Tgmob3jUiTWY3W5U=QpvxOCo_Erc5pi7cFg6oxG2_30mcxLg@mail.gmail.com>
	<CAMm1aWZEVrRYmxC_+2P695mhHLj1EHa=H5L4Le05Cd6H7nOLvA@mail.gmail.com>
	<CA+TgmobbvJ-kpzuQ+oyrFP4bLbbuRBsff1M+UPLhMHsD6DYPAA@mail.gmail.com>
	<CAMm1aWYKXZB0=hMxD7yL_vTNLZScwu7ThXZnYZ4gMhVmzQ5Trg@mail.gmail.com>
	<CAMm1aWbg_jVm=dqzS1AZV4p6-u0Xfxcu0B9M0ptweG5gyzu-Mw@mail.gmail.com>

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





view thread (105+ messages)  latest in thread

Message-ID: <20210803131008.GU12533@telsasoft.com>
Permalink:  ../20210803131008.GU12533@telsasoft.com/
Also on:    postgresql.org/message-id/20210803131008.GU12533@telsasoft.com

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: pryzby@telsasoft.com, nitinjadhavpostgres@gmail.com, robertmhaas@gmail.com, bharath.rupireddyforpostgres@gmail.com, tgl@sss.pgh.pa.us, andres@anarazel.de, sfrost@snowman.net, magnus@hagander.net, thomas.munro@gmail.com
  Subject: Re: when the startup process doesn't (logging startup delays)
  In-Reply-To: <20210803131008.GU12533@telsasoft.com>

* 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