Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
Date
Msg-id CA+TgmoZ=TNy5KXyOiUP_PwDXBAF-kEFO3=b0VKyug-H+pVhskw@mail.gmail.com
Whole thread Raw
In response to Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"  (Hannu Krosing <hannu@2ndQuadrant.com>)
Responses Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database"
List pgsql-hackers
On Thu, Jan 3, 2013 at 11:15 AM, Hannu Krosing <hannu@2ndquadrant.com> wrote:
> This is what I did with my sample pl/python function ;)

Yeah, except that the "c" in "ctime" does not stand for create, and
therefore the function isn't necessarily reliable.  The problem is
even worse for tables, where a rewrite may remove the old file and
create a new one.  I mean, I'm not stupid about this: when I need to
figure this kind of stuff out, I do in fact look at the file times -
mtime, ctime, atime, whatever there is.  Sometimes that turns out to
be helpful, and sometimes it doesn't.  An obvious example of the
latter is when you're looking at a bunch of files that have just been
untarred from a backup device.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Samuel Vogel
Date:
Subject: Print b-tree tuples
Next
From: Charles Gomes
Date:
Subject: Re: Writing Trigger Functions in C