Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iW8xn-0006iU-Jw for pgsql-bugs@arkaria.postgresql.org; Sun, 17 Nov 2019 01:02:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iW8xm-0003UX-Cd for pgsql-bugs@arkaria.postgresql.org; Sun, 17 Nov 2019 01:02:50 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iW8xm-0003UJ-4k for pgsql-bugs@lists.postgresql.org; Sun, 17 Nov 2019 01:02:50 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iW8xg-0003uP-LV for pgsql-bugs@lists.postgresql.org; Sun, 17 Nov 2019 01:02:49 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id xAH12dQt003392; Sat, 16 Nov 2019 20:02:39 -0500 From: Tom Lane To: dmitry.telpt@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16119: pg_dump omits columns specification for matviews In-reply-to: <16119-e64823f30a45a754@postgresql.org> References: <16119-e64823f30a45a754@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Fri, 15 Nov 2019 22:16:51 +0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3390.1573952559.1@sss.pgh.pa.us> Date: Sat, 16 Nov 2019 20:02:39 -0500 Message-ID: <3391.1573952559@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk PG Bug reporting form 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