From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: rajan <vgmonnet@gmail.com>
To: pgsql-admin@postgresql.org
Subject: Re: WAL restoration is not happening completely
Date: Fri, 18 Nov 2016 12:19:25 -0500
Message-ID: <c9a040c0-9f60-5ac3-3b3e-bf2d3196ca9d@2ndquadrant.com> (raw)
In-Reply-To: <1479467832483-5930928.post@n3.nabble.com>
References: <1479116970057-5930204.post@n3.nabble.com>
<aa031ba7-eda4-08ad-b553-80e1171a72bc@2ndquadrant.com>
<20161114175509.3wgvxos44hxxz26i@alap3.anarazel.de>
<1479467832483-5930928.post@n3.nabble.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-admin>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: peter.eisentraut@2ndquadrant.com, vgmonnet@gmail.com
Subject: Re: WAL restoration is not happening completely
In-Reply-To: <c9a040c0-9f60-5ac3-3b3e-bf2d3196ca9d@2ndquadrant.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox