| From: | Johannes Truschnigg <johannes(at)truschnigg(dot)info> |
|---|---|
| To: | LEROY TENNISON <leroy_tennison(at)prodigy(dot)net> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: archive_command options? |
| Date: | 2019-04-04 11:36:57 |
| Message-ID: | 20190404113657.x6gmvoztvqeew76y@vault.lan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Hello Leroy,
I was unhappy with the situation you described as well, and wrote a trivial
(but better -- although not perfect :)) replacement in C a while ago. You can
find it at [0]. It has served us well for the past five or so years, handling
hundreds of GB of WAL archives each day. Maybe you find it useful, too.
[0]: https://johannes.truschnigg.info/code/pg_archive_wal_segment-2.0.0/
--
with best regards:
- Johannes Truschnigg ( johannes(at)truschnigg(dot)info )
www: https://johannes.truschnigg.info/
phone: +43 650 2 133337
xmpp: johannes(at)truschnigg(dot)info
Please do not bother me with HTML-email or attachments. Thank you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Prince Pathria | 2019-04-04 12:40:13 | Re: Configuration of django with master slave replication Postgres |
| Previous Message | Jerry Sievers | 2019-04-04 00:18:24 | Re: archive_command options? |