| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 22:38:28 |
| Message-ID: | 49E3BEE4.6010706@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>> - what if I need to know about operators, operator classes, schemas, etc
>> etc
> Fine, let's log this info for those too (or else decide they're too
> obscure and don't - pg_class and pg_proc are certainly the most
> interesting cases).
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.
This would also supposedly allow us to track drops if we wanted.
We'd have to check on overhead of this, though, and maybe make it a GUC
to track it.
This would also be tremendously useful to suppliment replication systems.
--
Josh Berkus
PostgreSQL Experts Inc.
www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-04-13 23:06:09 | Re: proposal: add columns created and altered to pg_proc and pg_class |
| Previous Message | - - | 2009-04-13 21:11:21 | Re: Unicode support |