If an exclusive backup API is really removed from #PostgreSQL, new extension supporting an exclusive one may need to be implemented.
Meh. It's considerably easer to script the new thing wrongly than the old thing. It's far from easy to script keeping a postgres connection open in the background, with proper error checking, than with the old interface. Both are obviously easy to get wrong.
-
-
I agree the new one does not provide easy scriptability. I just don't agree the old one does, or does better.
-
I mean obviously the old interface has issues around the system / script dying in the wrong moment, but I don't understand how having to keep a connection open doesn't increase difficulty.
- 8 more replies
New conversation -
-
-
If psql's \exec allowed to check for errors it'd be a bit easier. If you want to shell script it, the best bet imo at the moment is to to \exec the copying of the data dir surrounded by start/stop backup. The overall script checks whether copy succeeded by checking a stamp file.
-
But that's ridiculous.
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.