Re: pg_upgrade and materialized views

From: Victor Yegorov <vyegorov(at)gmail(dot)com>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: pg_upgrade and materialized views
Date: 2018-02-21 09:46:30
Message-ID: CAGnEboipw-MY+beePKfhYO9c+Vqi_c44n-Fhr+2vN4H5VDHMnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

2018-02-21 0:56 GMT+02:00 Claudio Freire <klaussfreire(at)gmail(dot)com>:
>
> Well, the attached script reproduces the issue.
>
> Make a scratch dir somewhere, cd into it, and run it. It will download
> 9.6.7 and 10.2, build them, create a test db in 9.6.7, modify it a bit
> here and there to get to the desired state, pg_upgrade it to 10.2 and
> vacuum.
>
> Might even be a good idea to create a regression test with that, but
> AFAIK there's nothing remotely like that in the current tests.
>
> The patch you propose makes the test succeed. It may be true that
> there might be other similar issues lurking in that code, but it looks
> like it fixes this particular issue.
>

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

--
Victor Yegorov

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tomas Vondra 2018-02-21 14:31:04 Re: Segmentation Fault in logical decoding get/peek API
Previous Message Sudalai 2018-02-21 07:18:58 Re: Segmentation Fault in logical decoding get/peek API