On Fri, Nov 4, 2016 at 1:19 PM, Jeff Janes <jeff.janes@xxxxxxxxx> 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. -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
