Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id 2BCF02E0052 for ; Mon, 26 May 2008 15:18:55 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 36811-01 for ; Mon, 26 May 2008 15:18:50 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from lion.animals (mail.refractions.net [24.68.236.214]) by developer.postgresql.org (Postfix) with ESMTP id 81C0A2E004D for ; Mon, 26 May 2008 15:18:52 -0300 (ADT) Received: by lion.animals (Postfix, from userid 88) id B301AED0301; Mon, 26 May 2008 11:18:51 -0700 (PDT) Received: from [192.168.50.44] (unknown [192.168.50.44]) by lion.animals (Postfix) with ESMTP id 4E2B2ED02B0 for ; Mon, 26 May 2008 11:18:51 -0700 (PDT) Message-ID: <483AFEFD.2000504@refractions.net> Date: Mon, 26 May 2008 11:18:37 -0700 From: Kevin Neufeld User-Agent: Thunderbird 2.0.0.14 (Windows/20080421) MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: table creation/modification datestamp Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200805/222 X-Sequence-Number: 29306 As a DBA, it would be extremely useful to know when tables have been created or modified. PostgreSQL doesn't keep track of this, does it? (Table modification, in my mind, includes INSERTs, DELETEs, UPDATEs, and changes performed via ALTER TABLE. It does not include physical changes that may occur on the table due to VAACUMing or CLUSTERing.) Obviously, I can't use the relfilenode attribute in pg_class to check for table modification and look up the file's timestamp, since the OS updates the timestamp whenever physical changes occur. Further, I don't think linux even tracks a file's creation timestamp. The stats collector already tracks when a table was last ANALYZED, it would be nice to expand this functionality to include table creation/modification times. (Ideally, table timestamp record keeping should be persistent over db dumps and restores.) Cheers, Kevin