Dimitri,
* Dimitri Fontaine (dimitri@2ndQuadrant.fr) wrote:
> Here's a complete test case that works with my current branch, with a
> tricky test while at it, of course:
Apparently I've managed to miss the tricky case..?
Sure, dropping tables, schemas, etc, would have an impact on the values.
Dropping a table and then recreating it would be akin to deleteing a row
and then inserting a new one- the create value would be set to the time
of the new table being created and information about the dropped table
would be lost.
I'm not thinking of this as audit tracking where every action is logged.
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.
Thanks,
Stephen