On 2013-01-03 11:03:17 +0100, Hannu Krosing wrote:
> 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 ?
Because too many things change those. Moving to a different tablespace,
a rewriting ALTER TABLE, etc.
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
In response to
pgsql-hackers by date
|Next:||From: Pavel Stehule||Date: 2013-01-03 10:20:09|
|Subject: Re: Proposal: Store "timestamptz" of database creation on "pg_database"|
|Previous:||From: Hannu Krosing||Date: 2013-01-03 10:03:17|
|Subject: Re: Proposal: Store "timestamptz" of database creation