| From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Joao Junior <jcoj2006(at)gmail(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: archive_command too slow. |
| Date: | 2016-11-04 22:30:32 |
| Message-ID: | CAGTBQpY-TS2GM1FnfAQUdHvvK86a1a-Ntw6s83w3OU2Fwu-=yA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Fri, Nov 4, 2016 at 1:19 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> If setting up the ssh tunnel is the problem, you could assess whether you
> really need that security, or compile a custom postgresql with larger WAL
> file sizes, or write a fancy archive_command which first archives the files
> to a local directory, and then transfers them in chunks to the slave. Or
> maybe use streaming rather than file shipping.
Another option is to use ssh's ControlMaster and ControlPersist
features to keep the SSH tunnel alive between commands.
You'd have to set up the RSYNC_CONNECT_PROG environment variable on
your archive command for that and include the relevant options for ssh
in the command.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Justin Pryzby | 2016-11-05 22:36:37 | Re: no MCV list of tiny table with unique columns |
| Previous Message | Jeff Janes | 2016-11-04 16:19:19 | Re: archive_command too slow. |