| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Hannu Krosing <hannu(at)krosing(dot)net> |
| Cc: | 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: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Date: | 2013-01-03 13:15:51 |
| Message-ID: | 20130103131551.GA16126@tamriel.snowman.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Hannu Krosing (hannu(at)krosing(dot)net) 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, as noted before, those aren't always going to be correct.
Database files can be rewritten and recreated based on certain commands
(eg: CLUSTER). Perhaps there's a fork that isn't, but that almost seems
like it's more painful to try and figure out than just hooking in with
the CREATE command.
Thanks,
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-01-03 13:17:46 | Re: Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Previous Message | Stephen Frost | 2013-01-03 13:13:11 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |