Mark,
* Mark Kirkwood (mark.kirkwood@catalyst.net.nz) wrote:
> Ok, that is interesting. In my experience, provided the a)
> construction you are using in archive_command correctly reports
> success/failure, and b) you have some monitoring that checks for
> archive failure then that requirement of you having the required
> logs will be fine. Finally that c) your pg_basebackup concoction
> properly checks return codes then you are fine.
>
> All these are reasonably straightforward to implement via shell.
Sure, that'll work much of the time, but that's about like saying that
PG could run without fsync being enabled much of the time and everything
will be ok. Both are accurate, but hopefully you'll agree that PG
really should always be run with fsync enabled.
> Also, if what you are suggesting were actually the case, almost
> everyone's streaming replication (and/or log shipping) would be
> broken all the time.
No, again, this isn't an argument about if it'll work most of the time
or not, it's about if it's correct. PG without fsync will work most of
the time too, but that doesn't mean it's actually correct.
> With respect to 'If I would like to develop etc etc..' - err, all I
> was doing in this thread was helping the original poster make his
> stuff a bit better - I'll continue to do that.
Ignoring the basic requirements which I outlined isn't helping him get
to a reliable backup system.
Thanks!
Stephen