Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bzO0Y-0000F3-8b for pgsql-admin@arkaria.postgresql.org; Wed, 26 Oct 2016 13:12:42 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bzO0W-0007If-QX for pgsql-admin@arkaria.postgresql.org; Wed, 26 Oct 2016 13:12:40 +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.84_2) (envelope-from ) id 1bzNyq-0005Mz-Jj for pgsql-admin@postgresql.org; Wed, 26 Oct 2016 13:10:56 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bzNyn-0007p4-7i for pgsql-admin@postgresql.org; Wed, 26 Oct 2016 13:10:55 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u9QDAng1016414; Wed, 26 Oct 2016 09:10:49 -0400 From: Tom Lane To: Poul Kristensen cc: Scott Mead , pgsql-admin@postgresql.org Subject: Re: PostgresSQL 9.5 and systemd autorestart but without replication. In-reply-to: References: Comments: In-reply-to Poul Kristensen message dated "Wed, 26 Oct 2016 11:57:46 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <16412.1477487449.1@sss.pgh.pa.us> Date: Wed, 26 Oct 2016 09:10:49 -0400 Message-ID: <16413.1477487449@sss.pgh.pa.us> X-Pg-Spam-Score: -3.2 (---) 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 Poul Kristensen writes: > Replica(hot_standby) server: > Is it normal behavior that PostgreSQL 9.6 does a very very slow > recovery restart point at 1/77472E5 in the pg_log > while doing this > postgres: startup process recovering 000000010000000100000077(this > process has run several days) If that's the standby server, that process will persist as long as it's in standby; it's what's responsible for applying WAL received by the walreceiver process. You should have been able to connect long before now, though. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin