| From: | Hannu Krosing <hannu(at)krosing(dot)net> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(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 10:03:17 |
| Message-ID: | 50E55765.3070809@krosing.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/28/2012 03:14 AM, Stephen Frost wrote:
...
> I agree that what I was suggesting would be possible to implement with
> event triggers, but I see that as a rather advanced feature that most
> users aren't going to understand or implement. At the same time, those
> more novice users are likely to be looking for this kind of
> information- being told "oh, well, you *could* have been collecting it
> all along if you knew about event triggers" isn't a particularly
> satisfying answer. That's my 2c on it. I agree that having the example
> in the docs would be nice- examples are always good things to include.
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 ?
----------------
Hannu
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-01-03 10:18:08 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |
| Previous Message | Pavel Stehule | 2013-01-03 08:16:59 | Re: Proposal: Store "timestamptz" of database creation on "pg_database" |