Re: proposal: add columns created and altered to pg_proc and pg_class - Mailing list pgsql-hackers

Pavel Stehule <pavel.stehule@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


pgsql-hackers by date:

Previous
From: Devrim GÜNDÜZ
Date:
Subject: Regression failure on RHEL 4 w/ PostgreSQL 8.4 beta1
Next
From: Pavel Stehule
Date:
Subject: Re: proposal: add columns created and altered to pg_proc and pg_class