Re: does postgres log the create/refresh of a materialized view anywhere?

On Tue, Dec 13, 2016 at 8:50 PM, Kevin Grittner <kgrittn(at)gmail(dot)com> wrote:

> On Tue, Dec 13, 2016 at 7:37 PM, Melvin Davidson <melvin6925(at)gmail(dot)com>
> wrote:
> > On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner <kgrittn(at)gmail(dot)com>
> wrote:
> >> On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco <postgres(at)2xlp(dot)com>
> wrote:
> >>
> >>> Is there a way to find out when a materialized view was
> >>> created/refreshed?
> >>
> >>> I can log this manually in postgresql if needed, but was hoping
> >>> there was some "timestamp" on the view in a system table.
> >>
> >> This is not currently tracked in the system catalogs.
>
> > This goes back to a discussion of my request to add relcreated
> > column to pg_class.
> > https://www.postgresql.org/message-id/CANu8FiyiRPGZ+gB=
> 1JAYryX3HXCuQnFLSFgdzfXSvLMJ-jTc5w(at)mail(dot)gmail(dot)com
> > Apparently the naysayers do not feel it is worthwhile.
>
> Do you see relcreated as being something to set anew whenever the
> data contents of a materialized view change due to the REFRESH
> command? I wouldn't have thought so, but I guess the problem with
> that proposal is that everyone has a different idea of what the
> semantics of the column would be. Suggesting that field as the
> solution here seems to reinforce that perception, anyway.
>
> --
> Kevin Grittner
> EDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

Originally, all I wanted was a column to record the creation date/time of
an object. One reason it was debunked was that it would lead
to a request for an additional column to record changes in objects. I
maintain that both can be done, but others disagree,

--
*Melvin Davidson*
I reserve the right to fantasize. Whether or not you
wish to share my fantasy is entirely up to you.