Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ewX6H-0003tB-Oa for pgsql-admin@arkaria.postgresql.org; Thu, 15 Mar 2018 17:55:38 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1ewX6E-0006mz-Qh for pgsql-admin@arkaria.postgresql.org; Thu, 15 Mar 2018 17:55:34 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ewX6E-0006mn-12 for pgsql-admin@lists.postgresql.org; Thu, 15 Mar 2018 17:55:34 +0000 Received: from resqmta-ch2-11v.sys.comcast.net ([2001:558:fe21:29:69:252:207:43]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1ewX65-0001A4-4j for pgsql-admin@postgresql.org; Thu, 15 Mar 2018 17:55:33 +0000 Received: from resomta-ch2-10v.sys.comcast.net ([69.252.207.106]) by resqmta-ch2-11v.sys.comcast.net with ESMTP id wX5reIuNBNM3xwX5zeJibg; Thu, 15 Mar 2018 17:55:19 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20161114; t=1521136519; bh=pQoAhzxO5XhG2rFzHLyZCeY1wGU0ouzMO0uuwmt28T8=; h=Received:Received:Received:From:To:Subject:Date:Message-ID: MIME-Version:Content-Type; b=L4gyyxIJ4F408zlSxCISiZ+w4lT9fNNrxEhuwfV3D3Se5GoIJ0uGI4a2Azqq/RA+c 6GWvrN7takqRNPtM/v01OijR8BVKQvr8u1Ii5Ge93ONPqqDWb5hP1kU0j1jgJTnFxH /tGnsM1PuymYvrIPKbhkihryS3E1dnTFuCqUoxYQF6rUclKdIvkZzZ8o+jHsCnh9Q3 p1ygMiwp25WcTJhqxFB6y6yFAt4hTr9RR8QJdzNkFN0bgNmY1OFaHL72VmcN0a62+l aoLo1Ov6/zxF5o+dL0yRCtJkfAd+cMOn6Xb5w50DJauH4sgDEI9Q64Ta5tlFg/3dY/ rttk1NaEem5iQ== Received: from jsievers.comcast.net ([12.30.159.20]) by resomta-ch2-10v.sys.comcast.net with SMTP id wX5pezXDRk1NjwX5sewdMw; Thu, 15 Mar 2018 17:55:16 +0000 Received: from jsievers.enova.com (localhost [127.0.0.1]) by jsievers.comcast.net (Postfix) with ESMTP id A3E76260056 for ; Thu, 15 Mar 2018 12:55:09 -0500 (CDT) From: Jerry Sievers To: pgsql-admin@postgresql.org Subject: Wal fetching standby refuses to promote Date: Thu, 15 Mar 2018 12:55:09 -0500 Message-ID: <87a7v9rzpe.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: MS4wfMckfivkEW3Gh3FszGGDAVLzxXJhzETbtG8uAeEuiO/dI8ypCWD2S5THtOjUq5Lc/4wr+vVl0XkyyQWwb1fkjoiBBK8m/sj7mEw/vx6nwUOnu8MphQcW KwGBEMGa17UJ6ZgUrGA7m3GpNocdQkDBZHyfP7WOqO1bCxNDeGlAhSs/p42ANoJG46Rl5xlr615q+g== List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk This was an atomic snapshot put in recovery and happily reading WALs from the repo. It's consistent and allows read-only querying. It's replayed a few days worth of WALs and was previously running with a recovery_target_xid = $some-xid which apparently was never hit and/or aborted. It would not promote then, after pg_ctl promote. The 'promote' file did get created in pgdata. Now it's running again with recovery.conf that contains just... standby_mode = on restore_command = 'cp /somedir/%f %p' Still it fails to respond to the issuance of a promote. There is no trigger file config's in recovery.conf and we have never needed to do same since pg_ctl promote usually works. Any idea what's causing this? Thanks version ----------------------------------------------------------------------------------------------------------------- PostgreSQL 9.6.6 on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609, 64-bit (1 row) -- Jerry Sievers Postgres DBA/Development Consulting e: postgres.consulting@comcast.net p: 312.241.7800