On Mon, 2012-08-20 at 16:32 -0700, Josh Berkus wrote:
> This is sounding like a completely runaway spec on what should be a
> simple feature.
My feeling as well. However, we will eventually want to coalesce around
some best practices and make it easy and robust for "typical" cases.
> Personally, I would prefer a tool which just made it simpler to build my
> own triggers, and made it automatic for the history table to track
> changes in the live table. I think anything we build which controls
> what goes into the history table, etc., will only narrow the user base.
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.
Regards,
Jeff Davis
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
