From: | Patrick B <patrickbakerbr(at)gmail(dot)com> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | David Steele <david(at)pgmasters(dot)net>, Venkata B Nagothi <nag1010(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Wal files - Question | Postgres 9.2 |
Date: | 2016-11-29 10:59:56 |
Message-ID: | CAJNY3itqbMG7wAh8cc7sGWo8qT=BMGo0fKFhAzrNA13OvKCwCA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2016-11-29 16:36 GMT+13:00 David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>:
> On Mon, Nov 28, 2016 at 8:22 PM, Patrick B <patrickbakerbr(at)gmail(dot)com>
> wrote:
>
>>
>> Ho
>> [w]
>> is that even possible?? I don't understand!
>>
>>
> https://www.postgresql.org/docs/9.2/static/warm-standby.html
> """
>
> If you use streaming replication without file-based continuous archiving,
> you have to set wal_keep_segments in the master to a value high enough to
> ensure that old WAL segments are not recycled too early, while the standby
> might still need them to catch up. If the standby falls behind too much, it
> needs to be reinitialized from a new base backup. If you set up a WAL
> archive that's accessible from the standby, wal_keep_segments is not
> required as the standby can always use the archive to catch up.
> """
>
> Basically you did just that when you destroyed the archive. Apparently
> the master doesn't churn through WAL quickly enough to have had to discard
> the segments from the prior two hours.
>
> David J.
>
>
>
That was really helpful! Thanks David!
Patrick
From | Date | Subject | |
---|---|---|---|
Next Message | Berend Tober | 2016-11-29 11:11:36 | Re: Invoice Table Design |
Previous Message | Jerome Wagner | 2016-11-29 10:09:01 | Re: Storing files: 2.3TBytes, 17M file count |