Easy scriptability? Seems to be the only advantage.
-
-
I agree that we did, well over 10 years ago. I agree the new one isn't less hostile, and we should provide a less hostile option (actually, we do, in pg_basebackup, but it's also less flexible). But that doesn't mean we should keep around the hostile *and* dangerous option.
-
I was&am in favor of dropping the exclusive backup. Just think we ought to also do something to make the scripting of non-exclusive backups easier. Say by having the aforementioned wrapper doing the pg_start/stop_backup and then subshelling to a command, with args, for copying.
End of conversation
New conversation -
-
-
but per your previous suggestion perhaps all we actually need to do is ship a 5-10 line perl script that calls an external command to do the copying, and does the error checking on the postgres side?
-
I think it should be a C command, so it works easily on windows. But otherwise, yes.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.