Re: pg_upgrade and materialized views

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Victor Yegorov <vyegorov(at)gmail(dot)com>, Claudio Freire <klaussfreire(at)gmail(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_upgrade and materialized views
Date: 2018-02-21 23:49:43
Message-ID: 20180221234943.xagxfgvjkrrs4c3o@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On 2018-02-21 18:45:26 -0500, Tom Lane wrote:
> I've pushed a fix for this.

Thanks for this work, the new comments indeed make this much
clearer!

Wonder if we should include a comment in the release notes that possible
occurances of the problem can be fixed with REFRESH? Perhaps that's
obvious?

I also wonder if there's a chance that this can result in wrong query
results without getting errors, once the xids appears to be from the
future - if so, should we ask people to refresh matviews if they're
older than pg_upgrade?

Greetings,

Andres Freund

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2018-02-22 00:21:43 Re: pg_upgrade and materialized views
Previous Message Tom Lane 2018-02-21 23:45:26 Re: pg_upgrade and materialized views