Hi,
good point !
wal2Json seems to correspond to your needs,
this is first designed for Change Data Capture,
taht could generate a (very) big size of logs.
You didn't tell us much about your use case ...
and maybe, if the number of data modifications
is not too big, and the number of tables to track
limited, an history_table fed with (after insert,
after update, before delete)
triggers an other (simpler) solution ?
Regards
PAscal
--
Sent from: http://www.postgresql-archive.org/PostgreSQL-hackers-f1928748.html
