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 1v9HVr-00EWpf-Cj for pgsql-docs@arkaria.postgresql.org; Thu, 16 Oct 2025 06:30:58 +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 1v9HVq-00AO18-2a for pgsql-docs@arkaria.postgresql.org; Thu, 16 Oct 2025 06:30:57 +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 1v9HVp-00AO0z-RC for pgsql-docs@lists.postgresql.org; Thu, 16 Oct 2025 06:30:56 +0000 Received: from mail-pg1-x52f.google.com ([2607:f8b0:4864:20::52f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1v9HVm-002TNl-2u for pgsql-docs@lists.postgresql.org; Thu, 16 Oct 2025 06:30:56 +0000 Received: by mail-pg1-x52f.google.com with SMTP id 41be03b00d2f7-b555ab7fabaso310583a12.0 for ; Wed, 15 Oct 2025 23:30:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1760596252; x=1761201052; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=n1XJAVQYtilPIAfvzgch3LdVAnu5bq1xybQe8Wb89cI=; b=Bf4y0mv9oFvuMEtacz7oZoyuI1WcGkKoUH4A1sVaKR1FgFW/H/jvJ8VqsQJkPnRE9I 4c7Yr8dhXGPDUr+ffvUGLPYjN+dEXv6il4d1Y8GpOn1Pst8GvKRDUi6sqGyuNYJCZf2j pek7mL/lAmQ3AfX/pVAh0oqYnjBS1//KiBe9Dh7+egkMOG6x6PaxDZ1Wh1b7lwi5QYMU 1Qxtlm5qYv0OAEd7Jo+8gEyPOx4lzBYdrBjmfNsfQLix3T5EUvP2Td16U3XMF+u8iw+A F0crNZutAiK6LCa1WCpz5oqGVUwdJbAizL73jY4IykLaBXEHPNOCDOexoDfRQEVnQP6K OD3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1760596252; x=1761201052; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=n1XJAVQYtilPIAfvzgch3LdVAnu5bq1xybQe8Wb89cI=; b=sgSqol8V3PRtJd+cRzl4srgRbYKFqTZEucLLhiDweaP6OXfgNKzuYlBjhmMWR7FH3X 8JQ9Crpjy1KwlA6hsnePxcZurcqvAhWkBiKUyYpU5wTDSDZylEGqqFUPjXbyQKJ3Fjcd lUcIjSrQTtEC0X/9Ub2r8JIWw1pAW3unpEsiT+YsVxIi3DjHYNr1FQKsrlr1ibhhHSME F+mwYtlv42gGMZSzmSv1kvDKB3iaRNTr4dcAlZsN3rEcVqbSpEAaCgMgVLa8HdvTbndO CYsiUMx5uVz7+lecfKZQ/erPXPu9xfUY1INoBeSDIgLLhJuVcl7mk64nUndsTqEc6Ucl HNSA== X-Gm-Message-State: AOJu0YyA6D3Njv5vpOgKV7bPjL8E+StD2PkH8wwARJdQjmPz5SkW6+mh s+wrabiZPxyJ74AH36FqongIBng9gAWZ4WRQkCksC32NbewqjL9/unEQ4Sqf7JGKVgyWK8R1Q+3 Tv9V2/zr9q7oYPrWq5R2u0rYSjReRxX8= X-Gm-Gg: ASbGncu61KnpF0auUhRfIpTVkWXVFakoTZi3zsaNW19FtuPm0PeM/YF+1gRR7ZBATLH ndSAEQnpbmSuykqcy/m7VmAo2sDVjL48ZwKUEMxfVUam2tV2dS6EPappdJBSeipItj7u7/qfthU VOlDsW0CC/bun/BbpiSZ2lL4IuZojVlvZS01rn6hustSDqStCeqNWbNXtj3uKrQbLRV2Bstg+V9 nWTkgEBpTUV/ue7oc0MUfDAmWA2EVI6ZarDe2SDZ2CTu5B8/g4DFc8volfJCA== X-Google-Smtp-Source: AGHT+IGtF/MUel1aqRZ4NJcTYUy+6nwbumG/ssqjuzQzthG3rW/uEURZR1NbLfBzf7aIJ39cSvZoZykkIXrjvDbCc7s= X-Received: by 2002:a17:902:d607:b0:269:8f2e:e38 with SMTP id d9443c01a7336-29027356528mr399002425ad.6.1760596251855; Wed, 15 Oct 2025 23:30:51 -0700 (PDT) MIME-Version: 1.0 References: <176044409338.770.16064383081308443747@wrigleys.postgresql.org> In-Reply-To: From: Sergei Katkovsky Date: Thu, 16 Oct 2025 10:30:28 +0400 X-Gm-Features: AS18NWDBhg6126GFxGag1r5QykUBRvigR10vb7FNLyW_DW5dcLv7qGJluqaaYZc Message-ID: Subject: Re: BPCHAR description in 8.3. Character Types is misleading and incomplete To: Jeff Davis Cc: pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="0000000000002f4df7064140c2eb" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002f4df7064140c2eb Content-Type: text/plain; charset="UTF-8" Hello, > I think "blank-insignificant" is slightly better than "blank-ignoring". Yes, I agree. And there is also "blank-agnostic" if you prefer fancy expressions :) > Please take a look at the attached patch. If you'd like your name > included in the commit, please send it as you'd like it to appear. The patch is correct, in my opinion. Although it would be nice to have additionally a clear explanation in which contexts blanks in BPCHAR are insignificant (like in comparison) and in which they are still meaningful (like in concatenation), that issue could be addressed later separately, and maybe not even in the docs but rather in wiki. Regarding my name. I'm new to this list, so I didn't quite understand what you were asking for exactly. If you just need to know the spelling of my name, it's Sergei Katkoskii. With best regards, Sergei Katkovskii --0000000000002f4df7064140c2eb Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hello,

= >=C2=A0=C2=A0I think "blank-insignificant" is slightly better = than "blank-ignoring".

Yes, I agree. And there is also &qu= ot;blank-agnostic" if you prefer fancy expressions :)

>=C2=A0 Please take a look at the attached patch. If you'd= like your name
>=C2=A0 included in the commit, please send it as you= 'd like it to appear.

The patch is correct,=C2=A0in my opinion. = Although it=C2=A0would be nice to have additionally a clear=C2=A0explanatio= n in which contexts blanks in BPCHAR are insignificant=C2=A0(like in compar= ison) and in which they are still meaningful=C2=A0(like in concatenation), = that issue could be addressed later separately, and maybe not even in the d= ocs=C2=A0but rather in wiki.

Regarding my name. I'm new to this = list, so I didn't quite understand what you were asking for exactly. If= you just need to know the spelling of my name, it's Sergei Katkoskii.<= br>
With best regards,
Sergei Katkovskii
--0000000000002f4df7064140c2eb--