| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Hannu Krosing <hannu(at)krosing(dot)net> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net>, Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Date: | 2013-01-03 14:18:38 |
| Message-ID: | 50E5933E.6050907@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 1/3/13 6:34 AM, Hannu Krosing wrote:
>>> If what you want is something close to current unix file time semantics
>>> (ctime, mtime, atime) then why not just create a function to look up
>>> these
>>> attributes on database directory and/or database files ?
>> Because too many things change those. Moving to a different tablespace,
>> a rewriting ALTER TABLE, etc.
> Can't we actually fix these to preserve file creation date like tar does
> and still keep
> unix file semantics ?
I don't think that would be a good idea, because various file system
tools might actually want to look at, say, the mtime to know what to
back up. Also, none of those file attributes are the *creation* time,
so we wouldn't actually solve the original problem.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2013-01-03 14:22:36 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Previous Message | Pavel Stehule | 2013-01-03 14:18:02 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |