|
|
|
|
|
|
by chaps
2030 days ago
|
|
|
How would you be completely fucked when the rollback is to just rerun the workflow? Worst case scenario here is downtime, which is a far stretch from "completely fucked". It very much sounds like the databases that you work with and the databases that the article writer works with are used for two very, very different purposes. The author made no mentions about SLO-type requirements, so I think it's fair to say that SLO isn't a huge priority. But that can be mitigated, like I said, with a hot/warm/cold standby. Do you think it's a bad idea to use something like PostGIS because it uses functions that live on the database? |
|
|