Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svGxG-00DhZj-PM for pgsql-bugs@arkaria.postgresql.org; Mon, 30 Sep 2024 14:00:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1svGxF-000jr0-3a for pgsql-bugs@arkaria.postgresql.org; Mon, 30 Sep 2024 14:00:49 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svGxE-000jqs-RA for pgsql-bugs@lists.postgresql.org; Mon, 30 Sep 2024 14:00:48 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1svGxB-001qgI-6o for pgsql-bugs@lists.postgresql.org; Mon, 30 Sep 2024 14:00:48 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 48UE0iOo1450085; Mon, 30 Sep 2024 10:00:44 -0400 From: Tom Lane To: petrica.leuca@gmail.com cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #18642: Creating a materialized view on top of ts_stat succeeds on 16.4, but it fails on 17.0 In-reply-to: <18642-3fb95066fee227e9@postgresql.org> References: <18642-3fb95066fee227e9@postgresql.org> Comments: In-reply-to PG Bug reporting form message dated "Mon, 30 Sep 2024 09:06:15 -0000" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <1450083.1727704844.1@sss.pgh.pa.us> Date: Mon, 30 Sep 2024 10:00:44 -0400 Message-ID: <1450084.1727704844@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk PG Bug reporting form writes: > On PostgreSQL16 one can create a materialized view using ts_stat, but it > breaks on PostgreSQL17 due to no finding the table from the ts_stat query > (while the table does exist), please see below a test example. This is expected: you'll need to qualify the table name. See the very first compatibility entry in the v17 release notes. regards, tom lane