From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: add columns created and altered to pg_proc and pg_class |
Date: | 2009-04-13 18:32:28 |
Message-ID: | 19266.1239647548@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2009-04-13 18:33:47 | Re: proposal: add columns created and altered to pg_proc and pg_class |
Previous Message | Devrim GÜNDÜZ | 2009-04-13 18:28:22 | Regression failure on RHEL 4 w/ PostgreSQL 8.4 beta1 |