More log tables for database objects
Felix Kunde edited this page May 4, 2020
·
2 revisions
pgMemento provides an API to check out previous table or database states from the log tables into a separate database schema. So far, only the data is restored. It's not a real historic replica with views, constraints, indexes, sequences, domains, UDTs, UDFs, FDWs, rules, policies what so ever. At least, primary keys, foreign keys and indexes can be defined, but only on behalf of the current state. I thought about adding dedicated log tables for these three classes but it would require me to write new triggers and new restore and revert functions. This would take up much time where the real benefit might not be so great. As long as users are not requesting this feature it won't get implemented.
- Requirements
- Install pgMemento
- Initialize auditing
- Pause and restart logging
- End an audit trail
- Uninstall pgMemento
- Upgrade from v0.6 to v0.6.1
- Upgrade from v0.6.1 to v0.7
- Upgrade from v0.7 to v0.7.4
- Transaction_log
- Table_event_log
- Row_log
- Audit_schema_log
- Audit_table_log
- Audit_column_log
- Audit_tables VIEW
- Audit_tables_dependency VIEW