| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Devrim GÜNDÜZ <devrim(at)gunduz(dot)org> |
| Cc: | PostgreSQL Hackers ML <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Keeping creation time of objects |
| Date: | 2008-09-09 19:36:19 |
| Message-ID: | 22967.1220988979@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Devrim =?ISO-8859-1?Q?G=DCND=DCZ?= <devrim(at)gunduz(dot)org> writes:
> AFAICS, PostgreSQL is not keeping info about when a table, database,
> sequence, etc was created. We cannot get that info even from OS, since
> CLUSTER or VACUUM FULL may change the metadata of corresponding
> relfilenode.
> Does anyone think that adding a timestamp column to pg_class would bring
> an overhead?
There isn't sufficient support for such a "feature". In any case, why
would creation time (as opposed to any other time, eg last schema
modification, last data modification, yadda yadda) be especially
significant? Would you expect it to be preserved over dump/restore?
How about every other object type in the system?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | daveg | 2008-09-09 19:40:59 | Re: Keeping creation time of objects |
| Previous Message | Robert Haas | 2008-09-09 19:33:37 | Re: [PATCH] Cleanup of GUC units code |