| 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 17:33:44 |
| Message-ID: | 20180221173344.wjp4r6lxhcm35pzv@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2018-02-21 10:08:12 -0500, Tom Lane wrote:
> Victor Yegorov <vyegorov(at)gmail(dot)com> writes:
> > Is it possible, that bug #14852 is of the same nature as the issue at hand
> > here?
> > https://postg.es/m/20171013115320.28049.86457@wrigleys.postgresql.org
>
> For the archives' sake, the correct link is
> https://www.postgresql.org/message-id/20171013115320.28049.86457@wrigleys.postgresql.org
Yea, it does.
> Yeah, that does look suspiciously like a set of facts matching this
> problem :-(
I'd personally say ;), given that it's one less potentially data
corrupting bug to worry about ;). And it's one that can be fixed without
dataloss to boot.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-02-21 23:45:26 | Re: pg_upgrade and materialized views |
| Previous Message | Tom Lane | 2018-02-21 15:08:12 | Re: pg_upgrade and materialized views |