Hi Josh, I was quite busy last few months and I didn't have time to devote to this topic. I have read the feedbacks and want to make things move now.
I suggest, we can start by discussing the design of my solution: https://wiki.postgresql.org/wiki/SQL2011Temporal I expect any criticism and recommendations for making this solution acceptable. Regards, Miro First, note the change in topic. > This whole discussion has gone rather far afield from Miroslav's > original submission, which was for temporal tables, which is NOT the > same thing as audit logs, although the use cases overlap significantly. > Miroslav, I know this has been hard to follow, but you're getting a lot > of feedback because people are really interested in the feature and > related features. > >> That sounds like a good way to start. Actually, even before the tool, >> how about just some really good examples of triggers for specific kinds >> of audit logs, and some ways to run queries on them? I think that might >> settle a lot of these details. > > Well, I'm not adverse to solving some problems in the core: > 1) That it's difficult/impossible to write a completely generic audit > trigger which works with any table without utilizing an external SP > language like Python. > 2) That there's no obvious way to handle audit triggers and FK > relationships intelligently. > 3) That audit tables don't automatically track schema changes in the > live table. > 4) Checking which columns have changed (see Craig Ringer's email) > These seem like difficult enough challenges without getting more > complicated. > -- > Josh Berkus > PostgreSQL Experts Inc. > http://pgexperts.co
