Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c6Hm5-0007st-HZ for pgsql-admin@arkaria.postgresql.org; Mon, 14 Nov 2016 13:58:17 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c6Hm4-0002Pq-F5 for pgsql-admin@arkaria.postgresql.org; Mon, 14 Nov 2016 13:58:16 +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 1c6Hm3-0002PH-LZ for pgsql-admin@postgresql.org; Mon, 14 Nov 2016 13:58:15 +0000 Received: from out4-smtp.messagingengine.com ([66.111.4.28]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c6Hm0-0006YP-E4 for pgsql-admin@postgresql.org; Mon, 14 Nov 2016 13:58:14 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 478AD20715; Mon, 14 Nov 2016 08:58:10 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute2.internal (MEProxy); Mon, 14 Nov 2016 08:58:10 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= smtpout; bh=fGHg3BtC26HP+Sh2DeIeDnkV5ig=; b=N1Zkma8rnozGQ1xUAox3 VhXJDTDGC83OY3v0LEkFoir/0uFaACOSe+lCwxyA4n3k8au48vajxWXGAcdrbAlJ 5lW6I9+NgI5uqeHmKP6nFgSyHXykcb6DvuaVZXcCiHp4tsJkZQXqWI2i2E2nLdEr 0IlbZfg4FSV2MtHb16jgXFU= X-ME-Sender: X-Sasl-enc: PcfkvPFNMWhj0xMmxMHeuM5KhdNS6bJvUQirgqtmJCPl 1479131890 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 07B7924420; Mon, 14 Nov 2016 08:58:10 -0500 (EST) Subject: Re: WAL restoration is not happening completely To: rajan , pgsql-admin@postgresql.org References: <1479116970057-5930204.post@n3.nabble.com> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Mon, 14 Nov 2016 08:58:14 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <1479116970057-5930204.post@n3.nabble.com> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 11/14/16 4:49 AM, rajan wrote: > *The restored database has changes which were done today and missing data > from changes did a couple of days before.* That is pretty much impossible. It is plausible to mess some of this up and end up with a database instance that is missing the trailing end of changes because recovery aborted early somehow. But missing changes *in the middle* is not possible, unless you are encountering a serious bug. I suggest that there is some other confusion or misunderstanding going on. Just to be sure, make sure you are using the latest minor version. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin