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

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: Kevin Grittner <kgrittn(at)gmail(dot)com>, Jonathan Vanasco <postgres(at)2xlp(dot)com>, "pgsql-general(at)postgresql(dot)org general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: does postgres log the create/refresh of a materialized view anywhere?
Date: 2016-12-14 05:03:47
Message-ID: CAB7nPqSWgUFBBfg08qEF0vNzqpq8kszwvBzXeSJbUEigpV7x3g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Dec 14, 2016 at 11:19 AM, Melvin Davidson <melvin6925(at)gmail(dot)com> wrote:
> 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,

Event triggers could be used to track the creation or drop timestamp
of objects. Even if it is not supported for REFRESH, it may make sense
to support it in the firing matrix.
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Thomas Kellerer 2016-12-14 07:18:57 Re: pg_dump and quoted identifiers
Previous Message Michael Paquier 2016-12-14 04:59:50 Re: vacuum freeze in 96