@dev I get why you want to give non IT customers this option. It also sounds like an performance, storage nightmare o.O
Would a snapshot based solution be ok, or do you aim for the capability to rollback every single Transaction?
@dev Ok if rolling back to "snapshots" it pretty much sounds like: https://www.postgresql.org/docs/13/continuous-archiving.html#BACKUP-PITR-RECOVERY
(at least this is on my "need to fiddle with" list for similar reasons)
@gom yep! I know that one, but it's more of an admin/backup tool. There is no way an ordinary client can a) trigger a snapshot or b) query inside of one. Unless we build a lot of fiddly tooling around that.
@dev You do not wan't to offer it to customers but clients? I'm a bit confused.
Which kind of access do you want to grant and how easy should it be (maybe describe a workflow?).
Anyway, Postgres omitted "time travel" years ago (storage and performance issues) and recommends using triggers where needed.
Out there are DBS' with time traveling capabilities (Oracle calls it "flashback"), but you likely know that.
chaos.social – a Fediverse instance for & by the Chaos community