| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | fabriziomello(at)gmail(dot)com, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, Josh Berkus <josh(at)agliodbs(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Date: | 2013-01-03 14:30:12 |
| Message-ID: | 20130103143012.GB5506@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut escribió:
> If we're going to store object creation time, I think we should do it
> for all objects, stored in a separate catalog, like pg_depend or
> pg_description, keyed off classid, objectid. And have a simple C
> function to call to update the information stored there.
+1
We require two catalogs though, one shared, one database-local.
Would we track ctime of subsidiary objects such as constraints etc?
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2013-01-03 14:46:34 | Re: dynamic SQL - possible performance regression in 9.2 |
| Previous Message | Robert Haas | 2013-01-03 14:22:36 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |