From: | Charlton Galvarino <charlton(at)2creek(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: psql 8 warm standby strong start, weak finish |
Date: | 2015-04-30 20:49:00 |
Message-ID: | BY2PR0101MB1494099CC510AD93AFF07F7EFCD60@BY2PR0101MB1494.prod.exchangelabs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
>>> archiving run. Postgres will recycle WALs on its own when they are no
>>> longer needed. Or is there is some compelling reason you want to get rid
>of WALs?
>>
>> Ah. I didn't know that. I thought the cleanup was on me. Bonus!
>
>For more info take a look here:
>
>http://www.postgresql.org/docs/8.4/static/wal-configuration.html
Things are running smoothly so far. The proof will be in the pudding after 48h or so. But I have changed my rsync from its original pull approach to push. I do need to clean up the WAL's on master once they've made it to the warm_standby, so in this new push approach, I only round up WAL's that are, say 10m old, and then rsync those to warm_standby, deleting them on master when they've been xferred. warm_standby continues to do a good job of cleaning up the archive dir w/o any fuss from me.
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2015-04-30 23:15:51 | Re: psql 8 warm standby strong start, weak finish |
Previous Message | Dave Owens | 2015-04-30 19:08:40 | Re: database split |