From: | David Fetter <david(at)fetter(dot)org> |
---|---|
To: | PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Keeping creation time of objects |
Date: | 2008-09-10 00:06:03 |
Message-ID: | 20080910000603.GO573@fetter.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Sep 09, 2008 at 10:20:00PM +0300, Devrim GUNDUZ wrote:
> Hi,
>
> 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.
When people aren't keeping track of their DDL, that is very strictly a
process problem on their end. When people are shooting themselves in
the foot, it's a great disservice to market Kevlar shoes to them.
> Does anyone think that adding a timestamp column to pg_class would
> bring an overhead? For me, it looks a bit easy to add that value
> while calling CREATE XXX, but does anyone see a corner case?
As above, I am making a case for never attempting any such a thing,
and instead helping people understand that a casual attitude about
their DDL will result in cascading--usually catastrophic--failures.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-09-10 00:15:00 | Proposed patch: make SQL interval-literal syntax work per spec |
Previous Message | Greg Smith | 2008-09-09 22:55:38 | Re: [PATCH] Cleanup of GUC units code |