From: | Shaun Thomas <sthomas(at)optionshouse(dot)com> |
---|---|
To: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Introducing walctl, a simple tool for safe WAL management |
Date: | 2014-03-21 19:32:50 |
Message-ID: | 532C93E2.1020807@optionshouse.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello again,
Now that the open-source floodgates have been opened, I've been prepping
a couple of our applicable projects. This time, I've added this:
https://github.com/peak6/wallctl
It is a very simple PostgreSQL WAL management system that pushes or
pulls WAL files from a remote central storage server. It can be used to
fully replace archive_command or restore_command in handling WAL
archival or recovery.
It's designed to basically force WAL storage on a system that isn't a
master or standby server. The primary reasoning is that clusters may
have several replicas, so why expect the master to service all of them?
Master systems push WAL files to the remote archive, and slaves pull
from it; done.
It sets up each newly created clone as a streaming replica. In case of
disconnection, it uses restore_command to fetch the remote WAL files to
keep the slaves current. Something of a poor-man's self-healing.
Anyway, give it a look. I'll be the one looking over pull requests, so
if you have some improvements, I'd be glad to see them.
Later!
--
Shaun Thomas
OptionsHouse | 141 W. Jackson Blvd. | Suite 500 | Chicago IL, 60604
312-676-8870
sthomas(at)optionshouse(dot)com
______________________________________________
See http://www.peak6.com/email_disclaimer/ for terms and conditions related to this email
From | Date | Subject | |
---|---|---|---|
Next Message | Shaun Thomas | 2014-03-21 19:36:31 | Re: Introducing walctl, a simple tool for safe WAL management |
Previous Message | David Johnston | 2014-03-21 18:51:49 | Re: Passing array of range literals |