Trigger based logging alternative to table_log - Mailing list pgsql-general

From Jeff Janes
Subject Trigger based logging alternative to table_log
Date
Msg-id CAMkU=1yB4Znd+H60V-MyeuYThGRA60cf1kzjq1C3imoe8g2rTg@mail.gmail.com
Whole thread Raw
Responses Re: Trigger based logging alternative to table_log
Re: Trigger based logging alternative to table_log
Re: Trigger based logging alternative to table_log
List pgsql-general
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 in the new table for changes in the original.

The problem is that table_log hasn't been maintained in nearly 10 years, and pgfoundry itself seems to have one foot in the grave and one on a banana peel.

There are several other systems out there which store the data in hstore or json, which I would probably use if doing this from scratch.  But I'd rather preserve the existing log tables than either throw away that data, or port it over to a new format.

Is there any better-maintained code out there which would be compatible with the existing schema used by table_log?

Cheers,

Jeff

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: Request to add feature to the Position function
Next
From: Tom Lane
Date:
Subject: Re: migration to 9.6 array_accum memory issues