From: | Volkan YAZICI <yazicivo(at)ttmail(dot)com> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Keeping creation time of objects |
Date: | 2008-09-10 06:27:42 |
Message-ID: | 87hc8oqzvl.fsf@alamut.mobiliz.com.tr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, 9 Sep 2008, David Fetter <david(at)fetter(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.
>
> 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.
Word. In the company I'm currently working at we store database schema
in a VCS repository with minor and major version taggings. And there is
a current_foo_soft_version() function that returns the revision of the
related database schema. If there is no control over the database schema
changes in a company working scheme, the most logging-feature-rich
PostgreSQL release will provide an insignificant benefit compared the
mess needs to get fixed.
Regards.
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2008-09-10 06:35:45 | Re: Synchronous Log Shipping Replication |
Previous Message | Fujii Masao | 2008-09-10 06:15:29 | Re: Synchronous Log Shipping Replication |