Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dPW9A-0007JY-Dp for pgsql-admin@arkaria.postgresql.org; Mon, 26 Jun 2017 15:41:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dPW9A-0002Ry-0h for pgsql-admin@arkaria.postgresql.org; Mon, 26 Jun 2017 15:41:52 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dPW7J-0006Lb-Lt for pgsql-admin@postgresql.org; Mon, 26 Jun 2017 15:39:57 +0000 Received: from resqmta-po-05v.sys.comcast.net ([2001:558:fe16:19:96:114:154:164]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dPW7G-00069d-OX for pgsql-admin@postgresql.org; Mon, 26 Jun 2017 15:39:56 +0000 Received: from resomta-po-16v.sys.comcast.net ([96.114.154.240]) by resqmta-po-05v.sys.comcast.net with SMTP id PW7Bd3DnqrWIEPW7EdWHQN; Mon, 26 Jun 2017 15:39:52 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1498491592; bh=tAACfDnPcRJL78izaLRcSIkqc40XXPjEAaHiMRamYaA=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=lcCUqDIb+p4SFeUbOzCRJxRyPTbo2efcKtr2g49p93rr8uugCQtnHy7JEXWnVMkMQ E6Dh/YesxoIyqfIupKbH/DKw2xXIKf4PHqP9te9Ii7qfX1YEcwmgSumJPARvRjpJxw CXvJzm+H7Db4yJD0/vJP3m/AEILDE7kcKFM/mytxYb0w0MyREMyCIBOM1OfxecxXdy bsw44JTUayO+zSfrKkP6yTp8fIJ4d7hsenj/i1++7Fvyvcea5FcnZGj6UDPR3qZKWW ESHXhxnV4TvZ3CULCX8tY3rFDSgvq3Qnhz+gZmNpnBALcH9LFezwn5tgh5YRvQzu1a 8A3GUl/+oZjGA== Received: from jsievers.comcast.net ([12.30.159.20]) by resomta-po-16v.sys.comcast.net with SMTP id PW74dKA7MEIbEPW77dBGmQ; Mon, 26 Jun 2017 15:39:49 +0000 Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id 4B66626005E for ; Mon, 26 Jun 2017 10:39:42 -0500 (CDT) From: Jerry Sievers To: pgsql-admin@postgresql.org Subject: Restart time indication in cases of postmaster initiated all backend restart Date: Mon, 26 Jun 2017 10:39:42 -0500 Message-ID: <87fuemzrk1.fsf@jsievers.enova.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain X-CMAE-Envelope: MS4wfGdcOEfrTaeqn1fNUQKeukb/zwNuBMtzyVAKIuEi/G+YN6kBxdxqS+fMdd91EekvqgQOgzXuvZeS9Y31jvZBLdBFJjExqeb9szQ2AfVLFv3+i4Tb9yrd NTedy6lrzQNtHZ/ceq+RbAHAOhjdDhi13JfcM04a8c004EDNtlGwC1Y5jt+H9oxyTFJS2O/PuPYCcQ== List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org Admins, as per $subject, apart from server logs and/or client side diagnostics, is there a way to query for event time when a crashed backend restart happened? Such an event does *not* result in postmaster itself restarting and thus may lead to misleading confirmation of same. DBAs may be inclined to select pg_postmaster_start_time() to confirm. I have been aware of this fact for some time but I think less experienced admins get thrown by it sometimes. But to my question, is there some other function or equivalent method to read this from inside the DB that I'm not aware of? Thanks -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin