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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, 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 23:06:09
Message-ID: 24270.1239663969@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Josh Berkus <josh(at)agliodbs(dot)com> writes:
> I would suggest putting this info in a separate table, pg_change. It
> would have oid, catalog, user_changed, changed_on. That way we could
> simply keep the data for all objects which have an OID.

That makes more sense to me --- it would easily extend to all cases
and would not impose any overhead (in the form of useless columns)
for catalogs that you didn't want to track in a particular case.

The main problem that would have to be considered is how to flush
no-longer-useful entries (which of course entails deciding which
those are).

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-04-13 23:17:00 Re: join ordering
Previous Message Josh Berkus 2009-04-13 22:38:28 Re: proposal: add columns created and altered to pg_proc and pg_class