| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | rajan <vgmonnet(at)gmail(dot)com>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: WAL restoration is not happening completely |
| Date: | 2016-11-18 17:19:25 |
| Message-ID: | c9a040c0-9f60-5ac3-3b3e-bf2d3196ca9d@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tomasz Ziss | 2016-11-19 16:52:33 | Oracle Logical Standby equivalent in PostgreSQL |
| Previous Message | Achilleas Mantzios | 2016-11-18 16:31:33 | Effect of archive_mode , archive_command when set on the standby |