> From: Jeff Janes <jeff.ja...@gmail.com>
> To: "pgsql-general@postgresql.org" <pgsql-general@postgresql.org>
> Sent: Monday, 27 March 2017, 18:08
> Subject: [GENERAL] Trigger based logging alternative to table_log
>
> I have some code which uses tab
Jeff Janes schrieb am 27.03.2017 um 19:07:
I have some code which uses table_log
(http://pgfoundry.org/projects/tablelog/) to keep a log of changes to
selected tables. I don't use the restore part, just the logging
part.
It creates a new table for each table being logged, with several
> I have some code which uses table_log
> (http://pgfoundry.org/projects/tablelog/) to keep a log of changes to
> selected tables.
> I don't use the restore part, just the logging part.
> It creates a new table for each table being logged, with several additional
> columns, and adds
I have some code which uses table_log (
http://pgfoundry.org/projects/tablelog/) to keep a log of changes to
selected tables. I don't use the restore part, just the logging part.
It creates a new table for each table being logged, with several additional
columns, and adds triggers to insert rows
