Re: BUG #16119: pg_dump omits columns specification for matviews

Hi Tom,

Sorry for a little delay in response, there was no email access over the weekend =)
You know, everything that seems to be ugly for developer maybe 'desired' for customer and contrary in real world.

So, in our case, we're not owner or primary user of schema, only consume data that is maintained by another app and there is inter-team agreement that we can ONLY have views in their schema, that's a cause of such 'strange' solution.

Thanks for a fast feedback and great job!
Just a question, will the fix be back-ported to current supported branches like 9.4/9.5/9.6 or only included in 12?

Thank you again,
Dmitry

> On Nov 16, 2019, at 5:02 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
>> We've faced up with an issue how pg_dump exports materialzed views, it
>> doesn't export columns declaration that is legal parameter of CREATE DDL
>> instruction.
>
> I figured out what was going wrong here and pushed a fix for it.
> I'm still a bit curious about the real use-case, since a materialized
> view made from just a VALUES clause seems a bit pointless.
>
> regards, tom lane