Re: proposal: add columns created and altered to pg_proc and pg_class

From: Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, 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 19:50:42
Message-ID: 3073cc9b0904131250o37585362w5338522f787fa9b2@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Apr 13, 2009 at 1:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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;

while i agree with that, what i actually think will be useful is to
have the DDL log in a separate file... because it is a security log
and probably i will want different info than in a log to measure
average performance

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-13 20:15:44 Re: Unicode support
Previous Message Robert Haas 2009-04-13 19:45:17 Re: proposal: add columns created and altered to pg_proc and pg_class