| From: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Unable to recovery due missing wal_file |
| Date: | 2016-07-04 01:21:58 |
| Message-ID: | CAJNY3iuNM7qK_Zj7t9SykXBUN73LqYXiXBJFVkWcZhQQE2L7QQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>
>
>>
> 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?
>
Yes... it removes... I've changed to store them for up to 72h.
I'll restart the process now, by using stream instead fletch.
Let's see.... =\
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Boyd | 2016-07-04 01:25:29 | Re: psql connection option: statement_timeout |
| Previous Message | Craig Boyd | 2016-07-04 01:16:37 | Re: psql connection option: statement_timeout |