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 1oPqP0-0007aG-TJ for pgsql-docs@arkaria.postgresql.org; Sun, 21 Aug 2022 19:14:30 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1oPqOz-000661-Gr for pgsql-docs@arkaria.postgresql.org; Sun, 21 Aug 2022 19:14:29 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oPqOz-00065s-9U for pgsql-docs@lists.postgresql.org; Sun, 21 Aug 2022 19:14:29 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1oPqOt-0002XW-0h for pgsql-docs@lists.postgresql.org; Sun, 21 Aug 2022 19:14:28 +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 27LJELH74173835; Sun, 21 Aug 2022 15:14:21 -0400 From: Tom Lane To: Daniel Gustafsson cc: eric.mutta@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: Typo in description of PROGRAM parameter for the COPY command In-reply-to: References: <166104548566.654.11680826843612576896@wrigleys.postgresql.org> <1DC6647E-45CF-4ECD-BAB5-0CC0626AF121@yesql.se> <4169601.1661107714@sss.pgh.pa.us> Comments: In-reply-to Daniel Gustafsson message dated "Sun, 21 Aug 2022 21:07:36 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <4173833.1661109261.1@sss.pgh.pa.us> Content-Transfer-Encoding: quoted-printable Date: Sun, 21 Aug 2022 15:14:21 -0400 Message-ID: <4173834.1661109261@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Daniel Gustafsson writes: > Skimming the page I noticed that we wrap CSV in in all but a = few > places, which seemed randomly "chosen". Another sentence which stood ou= t to me > was this one on FREEZE: > "This violates the normal rules of MVCC visibility and users specifying > should be aware of the potential problems this might cause." > The use of "specifying" seems odd to me, removing it makes it read clear= er > IM-non-native-O. I suppose the author was aiming at "specifying it", but I agree that just dropping "specifying" works fine with fewer words. > The attached includes all the above suggestions. LGTM. regards, tom lane