From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andres Freund <andres(at)anarazel(dot)de> |
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:45:26 |
Message-ID: | 1695.1519256726@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2018-02-21 10:08:12 -0500, Tom Lane wrote:
>> 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.
I've pushed a fix for this. I concluded after further study that there
wasn't really much call for a unified notion of applicable relkinds,
because actually what this code is dealing with is "relkinds that need
preservation of dropped columns" and "relkinds that need preservation
of relfrozenxid", both of which are somewhat different from "relkinds
that have storage". What's really lacking is documentation, which
I attempted to supply. For the code change proper, I did what you
suggested and split the relfrozenxid hacking into an independent
if-block.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andres Freund | 2018-02-21 23:49:43 | Re: pg_upgrade and materialized views |
Previous Message | Andres Freund | 2018-02-21 17:33:44 | Re: pg_upgrade and materialized views |