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 1odYOd-0007Bf-Tp for pgsql-docs@arkaria.postgresql.org; Wed, 28 Sep 2022 14:50:47 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1odYOa-0006Q6-Sc for pgsql-docs@arkaria.postgresql.org; Wed, 28 Sep 2022 14:50:44 +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 1odYOa-0006PD-Ke for pgsql-docs@lists.postgresql.org; Wed, 28 Sep 2022 14:50:44 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1odYOV-0002th-MA for pgsql-docs@lists.postgresql.org; Wed, 28 Sep 2022 14:50:43 +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 28SEm3BN3946523; Wed, 28 Sep 2022 10:48:04 -0400 From: Tom Lane To: Laurenz Albe cc: yanliang lei , "pgsql-docs@lists.postgresql.org" Subject: Re: suggest about bpchar data type in the document In-reply-to: References: <120b3084.56b6.1833b5ffe4b.Coremail.msdnchina@163.com> <41fe0ea52f9803649ae876d4d14b2b7ca89ffc06.camel@cybertec.at> Comments: In-reply-to Laurenz Albe message dated "Wed, 28 Sep 2022 08:15:57 +0200" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3946521.1664376483.1@sss.pgh.pa.us> Date: Wed, 28 Sep 2022 10:48:03 -0400 Message-ID: <3946522.1664376483@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Laurenz Albe writes: >> I think that adding "bpchar(n)" in table 8.4 would be a good thing. > Here is a patch for that. There would need to be some mention of it in the paras below, too. regards, tom lane