Re: Reliable WAL file shipping over unreliable network - Mailing list pgsql-admin

From Rui DeSousa
Subject Re: Reliable WAL file shipping over unreliable network
Date
Msg-id 6056907B-551F-4ED0-804B-0FCACD39EB23@icloud.com
Whole thread Raw
In response to Re: Reliable WAL file shipping over unreliable network  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
Responses Re: Reliable WAL file shipping over unreliable network  (Mark Kirkwood <mark.kirkwood@catalyst.net.nz>)
List pgsql-admin
It looks like rsync is not handling the disk quota when actually syncing the file —  Disc quota exceeded (69) vs no
spaceleft (28).  It only fails if it can’t rename the truncated temp file — and in some cases there is just enough
spaceleft to allow the rename to succeed thus leaving a truncated WAL file.   

I’m using ZFS; and have 1GB quota on the given filesystem.

[postgres@hades ~/dbc1/pg_wal]$ rsync -a 000000010000005B00000035 ~/arch/dbc1/wal/000000010000005B00000035
rsync: rename "/usr/home/postgres/arch/dbc1/wal/.000000010000005B00000035.6bjO94" -> "000000010000005B00000035": Disc
quotaexceeded (69) 
rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1200) [sender=3.1.2]




pgsql-admin by date:

Previous
From: Ian Barwick
Date:
Subject: Re: WAL segment not replicated
Next
From: Mark Kirkwood
Date:
Subject: Re: Reliable WAL file shipping over unreliable network