On Wed, Dec 14, 2016 at 11:19 AM, Melvin Davidson 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
>
On Tue, Dec 13, 2016 at 8:50 PM, Kevin Grittner wrote:
> On Tue, Dec 13, 2016 at 7:37 PM, Melvin Davidson
> wrote:
> > On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner
> wrote:
> >> On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco
On Tue, Dec 13, 2016 at 7:37 PM, Melvin Davidson wrote:
> On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner wrote:
>> On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco wrote:
>>
>>> Is there a way to find out when a materialized view was
On Tue, Dec 13, 2016 at 7:36 PM, Kevin Grittner wrote:
> On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco
> wrote:
>
> > Is there a way to find out when a materialized view was
> > created/refreshed?
>
> > I can log this manually in postgresql if needed,
On Tue, Dec 13, 2016 at 5:57 PM, Jonathan Vanasco 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
Is there a way to find out when a materialized view was created/refreshed? I
couldn't find this information anywhere in the docs.
the use-case is that I wish to update a materialized view a few times a day in
a clustered environment. i'd like to make sure one of the redundant nodes
doesn't