Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1YbALO-000517-Q9 for pgsql-admin@arkaria.postgresql.org; Thu, 26 Mar 2015 16:09:18 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1YbALO-0005aI-1m for pgsql-admin@arkaria.postgresql.org; Thu, 26 Mar 2015 16:09:18 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1YbALN-0005aB-0O for pgsql-admin@postgresql.org; Thu, 26 Mar 2015 16:09:17 +0000 Received: from mailout.easymail.ca ([64.68.201.169]) by makus.postgresql.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.80) (envelope-from ) id 1YbALJ-0003bL-LC for pgsql-admin@postgresql.org; Thu, 26 Mar 2015 16:09:15 +0000 Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id D397AE56B; Thu, 26 Mar 2015 12:09:11 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -3.935 X-Spam-Level: X-Spam-Status: No, score=-3.935 required=5 tests=[ALL_TRUSTED=-1.8, AWL=-0.228, BAYES_00=-2.599, DNS_FROM_AHBL_RHSBL=0.692] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tWlus2z56Cmy; Thu, 26 Mar 2015 12:09:11 -0400 (EDT) Received: from [192.168.2.16] (unknown [8.39.228.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 3C936E569; Thu, 26 Mar 2015 12:09:11 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2070.6\)) Subject: Re: postgres hot-standby questions. From: Scott Ribe In-Reply-To: Date: Thu, 26 Mar 2015 10:09:08 -0600 Cc: "pgsql-admin@postgresql.org" Content-Transfer-Encoding: quoted-printable Message-Id: <604F46E7-7F6C-485B-BB72-21378D341F94@elevated-dev.com> References: <848F3721-4A21-4260-9640-8F698E3EE376@skogoglandskap.no> <3C08D5DD-0702-4136-BBE3-21CBE064ADDE@elevated-dev.com> To: "Graeme B. Bell" X-Mailer: Apple Mail (2.2070.6) X-Pg-Spam-Score: -2.6 (--) 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 On Mar 26, 2015, at 9:43 AM, Graeme B. Bell wrote: >=20 > Do you know if using the trigger file makes any change to the DB or WAL w= hich couldn't be replicated on the master when it comes back up?=20 No. It just signals PG to come out of continuous recovery mode and start al= lowing normal (read/write) operations. It also moves recovery.conf out of t= he way (to recovery.done) so that if PG is restarted, it does NOT go back i= nto recovery mode and start trying to get updates from the former master. > I could try to script it using e.g. pg_last_xlog_receive_location, pg_la= st_xlog_replay_location, but that doesn't help so much when the DB decides = to complete shutdown while the packet is still on the wire, and the packet = goes missing.=20 Yeah, that mostly tells you if your network is faster than your disk. (OK, = not really, but you obviously know what I mean...) But try comparing pg_cur= rent_xlog_location on the master to pg_last_xlog_receive_location on the re= plica. You could also look into using the pg_stat_replication view.=20 --=20 Scott Ribe scott_ribe@elevated-dev.com http://www.elevated-dev.com/ https://www.linkedin.com/in/scottribe/ (303) 722-0567 voice --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin