Re: Reliable WAL file shipping over unreliable network

From: Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz>
To: Rui DeSousa <rui(dot)desousa(at)icloud(dot)com>
Cc: Dianne Skoll <dfs(at)roaringpenguin(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org
Subject: Re: Reliable WAL file shipping over unreliable network
Date: 2018-03-01 03:46:41
Message-ID: 06dd8b81-8b1a-ae5c-8ddd-1556b5946176@catalyst.net.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Hi

On 01/03/18 15:27, Rui DeSousa wrote:
> STS is initialized as 3; and is only set to zero if rsync returns zero.
>
>

Ok, so if that works set correctly then another possibility is the
archive filesystem (what is that BTW?) not handling out of space
nicely/properly. I'm thinking this because doing some testing against a
small ext4 filesystem finds rsync reliably returning 11 when trying to
copy a file that will not fit (version 3.1.2).

regards
Mark

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Ian Barwick 2018-03-01 04:51:28 Re: WAL segment not replicated
Previous Message Ted EH 2018-03-01 02:43:48 WAL segment not replicated