| 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-21 00:22:06 |
| Message-ID: | CAGTBQpZzkAZ21rrchMeABXLbQnAtR9yadr7_j_K2ZmXS1oirnw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Feb 20, 2018 at 8:44 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Claudio Freire <klaussfreire(at)gmail(dot)com> writes:
>>> Well, the attached script reproduces the issue.
>
> One thing this doesn't prove by itself is whether the use of
> REFRESH MATERIALIZED VIEW CONCURRENTLY has any effect on the
> situation.
>
> I poked at that a bit and noted that REFRESH MATERIALIZED VIEW
> CONCURRENTLY doesn't seem to change the matview's relfrozenxid
> at all, while a plain REFRESH advances the matview's relfrozenxid
> to (more or less) the current xid counter.
Probably the reason why only concurrently triggers the vacuum
assertion is because only concurrently creates dead tuples.
Vacuum won't check unless there are dead tuples, it skips all-visible pages.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-21 00:23:57 | Re: pg_upgrade and materialized views |
| Previous Message | Andres Freund | 2018-02-21 00:06:25 | Re: pg_upgrade and materialized views |