4 ms·
I can definitely see the demand for something like this, but the engineering on it becomes quite difficult. Without the ability to cancel long running queries t
by craigkerstiens 10y ago
I can definitely see the demand for something like this, but the engineering on it becomes quite difficult. Without the ability to cancel long running queries there can be some replication lag and the WAL disk could fill up. Without actual administrative access to the instance it becomes very hard to fully guarantee such replication.
If you do want this more out of the box the real options today are either built it yourself or choose a provider that's delivering it.
- EmielMols 10y agoI don't think this is a huge problem. Yes, long running queries might introduce lag. When this lag hits a threshold of your choosing, PGBackup (or any service that would offer it) would then gladly send out pager alerts. The same would happen if the WAL could not be retrieved in time (because wal storage full): PGBackup would start a new base_backup and send out pager alerts.