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 1qY0PX-000Xeq-5T for pgsql-docs@arkaria.postgresql.org; Mon, 21 Aug 2023 08:37:19 +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 1qY0PU-004JcX-Vg for pgsql-docs@arkaria.postgresql.org; Mon, 21 Aug 2023 08:37:16 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qY0PU-004Jc9-GR for pgsql-docs@lists.postgresql.org; Mon, 21 Aug 2023 08:37:16 +0000 Received: from mout-u-107.mailbox.org ([80.241.59.207]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qY0PQ-0007Na-3c for pgsql-docs@lists.postgresql.org; Mon, 21 Aug 2023 08:37:14 +0000 Received: from smtp202.mailbox.org (smtp202.mailbox.org [IPv6:2001:67c:2050:b231:465::202]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-384) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-u-107.mailbox.org (Postfix) with ESMTPS id 4RTm726pT5z9sNb; Mon, 21 Aug 2023 10:37:02 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ewie.name; s=MBO0001; t=1692607023; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=UPu9/N1nBShdao3/tOVJ6sCzIQUvAoDKnsXJ1xcAHWw=; b=w20GIrpOSw+YH3TDEjyqJWdh2rwWh5EQQvkL7o2pRpXLCYdzFCYwYb3GtISGVA3KK9OO4m EzaeTESyV0RIwePcScwlEIKBPaJkUsHIB7rsoqnrVKvLS4qBG0Nk1UJSdzu06xWELvdix+ Z4+zzm3fDRsgyHZBml3ywXPCqk35MyMJaoFwUuJ0mS/nL6OAgv/eZ6iBXGoaK9bJD9xXGr Nv3cig8ZqJHqSeRpwIkwm+6euBiSa3auY7daZnEEKmlKzCu3A6ccqFcG5HjjFOoMQqifTK MqhfVjiQBlBpdDURmXkkw/mym3UWc2ANA5wN3ZiuyJA8B/upJt12DDC/jgd9Nw== Date: Mon, 21 Aug 2023 10:37:02 +0200 (CEST) From: Erik Wienhold To: mark.meeus@gmail.com, pgsql-docs@lists.postgresql.org Message-ID: <1300044510.104825.1692607022369@office.mailbox.org> In-Reply-To: <169260135718.628.3175598120953717107@wrigleys.postgresql.org> References: <169260135718.628.3175598120953717107@wrigleys.postgresql.org> Subject: Re: Wrong statement on the materialized views page MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Priority: 3 Importance: Normal X-Rspamd-Queue-Id: 4RTm726pT5z9sNb List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 21/08/2023 09:02 CEST PG Doc comments form wrote: > > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/15/rules-materializedviews.html > Description: > > There might be an issue on this page: > https://www.postgresql.org/docs/current/rules-materializedviews.html > > I think the statement > CREATE TABLE mymatview AS SELECT * FROM mytab; > should actuall be > CREATE VIEW mymatview AS SELECT * FROM mytab; No, CREATE TABLE is correct in this case because that section is about the persistence of matview results like a table. -- Erik