From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Unable to recovery due missing wal_file |
Date: | 2016-07-04 00:55:45 |
Message-ID: | e72f01a4-4d3c-2992-747c-355deedd590d@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 07/03/2016 05:36 PM, Patrick B wrote:
> I don't have it now!
>
> But I didn't know that postgres would need that file! If I knew it, I'd
> have checked just after pg_basebackup started....
Not sure that would have mattered for the reasons below.
You might want to take a look at the below:
https://www.postgresql.org/docs/9.5/static/wal.html
In particular:
https://www.postgresql.org/docs/9.5/static/wal-intro.html
Short version WAL files are essential to restoring and on the
originating server are recycled, subject to the configuration parameters
explained here:
https://www.postgresql.org/docs/9.5/static/wal-configuration.html
So the wal archiving you have set up is not storing everything, it
removes older files over time?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Boyd | 2016-07-04 01:16:37 | Re: psql connection option: statement_timeout |
Previous Message | Patrick B | 2016-07-04 00:36:29 | Re: Unable to recovery due missing wal_file |