Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1c7mqg-00035A-CG for pgsql-admin@arkaria.postgresql.org; Fri, 18 Nov 2016 17:21:14 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1c7mqf-0000um-VF for pgsql-admin@arkaria.postgresql.org; Fri, 18 Nov 2016 17:21:14 +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 1c7moy-0007Q0-RI for pgsql-admin@postgresql.org; Fri, 18 Nov 2016 17:19:28 +0000 Received: from out2-smtp.messagingengine.com ([66.111.4.26]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1c7mow-0007bI-Ft for pgsql-admin@postgresql.org; Fri, 18 Nov 2016 17:19:27 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id CD62B208A2; Fri, 18 Nov 2016 12:19:25 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Fri, 18 Nov 2016 12:19:25 -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=HpmdND4P1C9x4I9QLZbxtBBtBDw=; b=n1OXdMc1sIMXGgYSpblr RLr2RnXef+NvM2ZPlyUT5JO000k8fmddlLNgl3yEbGL3DzYoWMyix7YL3IEeUJE0 R0fIfpOMXofxxaOauxKWk+Oy0vc2w38rMadT0Y6TbYmBiU8Pzupl0HGwSlYdd7nV JmEATQIuP47SknEhHGdWLBM= X-ME-Sender: X-Sasl-enc: Se3lE9/BMeRK12uTvCYElqm9tkIJueDelSzcTFDQLPRA 1479489565 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 8DCEA7E2E1; Fri, 18 Nov 2016 12:19:25 -0500 (EST) Subject: Re: WAL restoration is not happening completely To: rajan , pgsql-admin@postgresql.org References: <1479116970057-5930204.post@n3.nabble.com> <20161114175509.3wgvxos44hxxz26i@alap3.anarazel.de> <1479467832483-5930928.post@n3.nabble.com> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: Date: Fri, 18 Nov 2016 12:19:25 -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: <1479467832483-5930928.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/18/16 6:17 AM, rajan wrote: > One thing I missed to update is that the Source(master) machine I was > running is switched off and on everyday. It may have caused any disruption > in the WAL files? Well, the point of the WAL is to preserve data integrity in case of crashes. So, no, that should normally not cause problems. > And one more question, The WAL files are created as 16MB segments, that is > obvious. But I do not know when the file is completely written. Is it like, > a file is created and then written till 16MB or 16MB data segment is > directly written at once. It is written in smaller chunks and then archived or rotated when the 16 MB are full. -- 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