Auto-Logging in PostgreSQL Friday 15:20 Hotel
Twitter: @davidfetter Blog: databasedoings.blogspot.com
I'm David Fetter.
I've worked in various commercial enterprises, non-profits and educational institutions. I am an PostgreSQL contributor, and have worked extensively with varied tools on transaction processing and analytics systems. Together with a small, intrepid group of others, I have helped found and grow user groups including the San Francisco PostgreSQL Users' Group.
I am always looking for ways to make the PostgreSQL-verse better.
Very much so. Both venues have provided, in addition to a rich hall track, excellent formal programs.
My talk is about a system to log DML changes in a way that makes them easy to query called changelog_trigger. I was motivated to do this talk by the fact that this software solves a problems I encountered over and over in my professional career in a clean and practical way.
Anyone who has ever wondered what went on in a database after a transaction is committed.
They should know what a database is, and what regret is. Apart from that, some idea of what data serialization (JSON, e.g.) is good for can help, as can a basic knowledge of what triggers are.