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 1r5uxl-00FuCI-V7 for pgsql-docs@arkaria.postgresql.org; Wed, 22 Nov 2023 21:40:49 +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 1r5uxk-00D1bN-HC for pgsql-docs@arkaria.postgresql.org; Wed, 22 Nov 2023 21:40:48 +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 1r5uxk-00D1bD-9b for pgsql-docs@lists.postgresql.org; Wed, 22 Nov 2023 21:40:48 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1r5uxh-006rz1-Dg for pgsql-docs@postgresql.org; Wed, 22 Nov 2023 21:40:46 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2023062407; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=AmAEDSpD62vcRvsRvxE/PBDKgK1/kVG8MzKN4BtC294=; b=R/UXA KGS3l5Ub2t6z2AV6PoDe+uQdUOhkXOQaWwEun5PONYVJZhEaX986o+voCRD07DFSQMltbG1z7g1Gt ti3NJ/weR72Q5bQMN3o/MGKh8Fh2pKOMVAYMEZesaA48+YIw0yMoy7EJUX0hWBNtsMd/sJ9cnMf0B Npt9DP8A+KVIdOWQ+Ax9GQoB8nzI/CObRqrqGn+MU+11yCm8/uZSuzblLCr0slMIusk9CcB0DMaQz xB5i68zKBlE18Kq4/guD6+SbgqI9VSuxMY/oAedGUPZQg6dLX/J/qGLBzLFXR74wmZL5G5wERTfE7 s3WQFjbhZjAFz/PJS06EavyFDUVwg==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1r5uxg-00BLGu-1l; Wed, 22 Nov 2023 16:40:44 -0500 Date: Wed, 22 Nov 2023 16:40:44 -0500 From: Bruce Momjian To: ap@robillo.net Cc: pgsql-docs@postgresql.org Subject: Re: [DOCS] Double negation in parameter description Message-ID: References: <20170208152743.1411.6073@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="XylPLp8AahzGwdb6" Content-Disposition: inline In-Reply-To: <20170208152743.1411.6073@wrigleys.postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --XylPLp8AahzGwdb6 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Wed, Feb 8, 2017 at 03:27:43PM +0000, ap@robillo.net wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/sql-refreshmaterializedview.html > Description: > > In the description of the CONCURRENTLY parameter (3rd line/paragraph, the > statement employs double negation which makes it hard to read and > understand. > > "This option may not be used when the materialized view is not already > populated." > > I guess the author would want to mean: > > "This option may only be used on a populated materialized view."? > > Your clarification is much appreciated. I know this is six years old, but fixed in master with the attached patch. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Only you can decide what is important to you. --XylPLp8AahzGwdb6 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="master.diff" diff --git a/doc/src/sgml/ref/refresh_materialized_view.sgml b/doc/src/sgml/ref/refresh_materialized_view.sgml index 675d6090f3..7a019162c3 100644 --- a/doc/src/sgml/ref/refresh_materialized_view.sgml +++ b/doc/src/sgml/ref/refresh_materialized_view.sgml @@ -67,7 +67,7 @@ REFRESH MATERIALIZED VIEW [ CONCURRENTLY ] nameWHERE clause. - This option may not be used when the materialized view is not already + This option can only be used when the materialized view is already populated. --XylPLp8AahzGwdb6--