Pavel Stehule <pavel.steh...@gmail.com> writes:
> this my proposal is very simple. It help to people who have to manage
> large or complex database system. Important data are date of creating
> and date of altering tables and stored procedures. These data cannot
> be modified by user, so implementation doesn't need any new
> statements.
ISTM anyone who thinks they need this actually need a full DDL log;
or at least, if we give them this, they will be back next week asking
for a full log. So it'd save a lot of work to tell them to just log
their DDL to start with.
Some obvious objections to the simple approach:
- what if I want to know *who* made the change
- what if I need to know about the change before last
- what if I need to know about a DROP
- what if I need to know about operators, operator classes, schemas, etc
etc
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
