PostgreSQL-only database-level audit logging of all databases changes using a completely transparent stored procedure and triggers. Comes with specs for your project and a rake task to generate the reverse SQL to undo changes logged.
All SQL INSERTs, UPDATEs, and DELETEs will be captured. Record columns that do not change do not generate an audit log entry.
-
First, enable plpgsql langauges in your postgresql instance. Execute the following as a superuser in postgres make sure your database has plpgsql enabled:
CREATE OR REPLACE PROCEDURAL LANGUAGE plpgsql; -
Generate the appropriate Rails files:
rails generate pg_audit_log:install
The PgAuditLog::Entry ActiveRecord model represents a single entry in the audit log table. Each entry represents a single change to a single field of a record in a table. So if you change 3 columns of a record, that will generate 3 corresponding PgAuditLog::Entry records.
You can see the SQL it injects on every query by running with LOG_AUDIT_SQL
Running rake db:migrate will install the audit log table, as well as the triggers and functions needed for pg_audit_log to work properly.
TODO
Since schema.rb cannot represent TRIGGERs or FUNCTIONs you will need to set your environment to generate SQL instead of Ruby for your database schema and structure. In your application environment put the following:
config.active_record.schema_format = :sql
And you can generate this sql using:
rake db:structure:dump
rake pg_audit_log:uninstall
On a 2.93GHz i7 with PostgreSQL 9.1 the audit log has an overhead of about 0.0035 seconds to each INSERT, UPDATE, or DELETE.
- ActiveRecord
- PostgreSQL
- Rails 3.2, 4.x
Copyright © 2010–2014 Case Commons, LLC. Licensed under the MIT license, available in the “LICENSE” file.