From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: pg_upgrade and materialized views |
Date: | 2018-02-20 21:44:53 |
Message-ID: | CAGTBQpZp-d9otMRuwtRJEVS144MrrK9SGzYwesCAXNyjNDTKWg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Feb 20, 2018 at 6:27 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> (2) independently of that, it sounds like REFRESH
> MATERIALIZED VIEW CONCURRENTLY is somehow preventing advancement of the
> matview's relfrozenxid in the source DB.
About that, I did check the view's relfrozenxid and its rows' xmin to
see if there was some obvious breakage.
The following query:
select * from device_specs_ranking_mv where age(xmin) > age((select
relfrozenxid from pg_class where relname = 'device_specs_ranking_mv'))
limit 1;
Yields empty results both in the master and the replica, which, unless
I did something wrong in that query, would rule out replication
issues.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2018-02-20 21:46:48 | Re: pg_upgrade and materialized views |
Previous Message | Claudio Freire | 2018-02-20 21:38:50 | Re: pg_upgrade and materialized views |