From: Tom Lane <tgl@sss.pgh.pa.us>
To: dmitry.telpt@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16119: pg_dump omits columns specification for matviews
Date: Sat, 16 Nov 2019 20:02:39 -0500
Message-ID: <3391.1573952559@sss.pgh.pa.us> (raw)
In-Reply-To: <16119-e64823f30a45a754@postgresql.org>
References: <16119-e64823f30a45a754@postgresql.org>
PG Bug reporting form <noreply@postgresql.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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, dmitry.telpt@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #16119: pg_dump omits columns specification for matviews
In-Reply-To: <3391.1573952559@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox