Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jZJS9-000868-2C for pgsql-bugs@arkaria.postgresql.org; Thu, 14 May 2020 19:23:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jZJS7-0002N0-3n for pgsql-bugs@arkaria.postgresql.org; Thu, 14 May 2020 19:23:31 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jZJS6-0002Mr-Tf for pgsql-bugs@lists.postgresql.org; Thu, 14 May 2020 19:23:30 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jZJS2-0002Tt-UH for pgsql-bugs@lists.postgresql.org; Thu, 14 May 2020 19:23:29 +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 04EJNN7T012582; Thu, 14 May 2020 15:23:23 -0400 From: Tom Lane To: Borys K cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16437: The dump is stored with error in creating VIEW statement. In-reply-to: References: <16437-5257db04508943ab@postgresql.org> <6545.1589476731@sss.pgh.pa.us> Comments: In-reply-to Borys K message dated "Thu, 14 May 2020 21:34:14 +0300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12580.1589484203.1@sss.pgh.pa.us> Date: Thu, 14 May 2020 15:23:23 -0400 Message-ID: <12581.1589484203@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk [ thanks for sending the off-list dump ] Borys K writes: > It is not a pure PostgreSQL server. > I am using https://www.timescale.com/ Well, you'd really need to take this up with them. This view seems to be using TimeScale-specific features, and I can't even tell whether it ought to be legal. The view would certainly not be legal in regular Postgres, because the table it's selecting from has no unique indexes at all, so there's no basis for allowing an abbreviated GROUP BY. I'm suspecting that TimeScale may have special provisions for dumping databases, because it's hard to see how this dump could be reloaded as-is. But I don't know much about that product. regards, tom lane