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.98.2) (envelope-from ) id 1xRQqk-00000000xnP-1rpw for pgsql-docs@arkaria.postgresql.org; Thu, 12 Nov 2026 09:12:06 +0000 Received: from localhost ([127.0.0.1]:60942 helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1xRQqj-0000000Fbac-1BVm for pgsql-docs@arkaria.postgresql.org; Thu, 12 Nov 2026 09:12:05 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]:53464) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xRQqi-0000000FbaU-3vxq for pgsql-docs@lists.postgresql.org; Thu, 12 Nov 2026 09:12:05 +0000 Received: from smtp.outgoing.loopia.se ([93.188.3.37]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1xRQqg-00000000cMg-3Z9Z for pgsql-docs@lists.postgresql.org; Thu, 12 Nov 2026 09:12:04 +0000 Received: from s807.loopia.se (localhost [127.0.0.1]) by s807.loopia.se (Postfix) with ESMTP id 2B7E37D809E for ; Thu, 12 Nov 2026 10:11:53 +0100 (CET) Received: from s980.loopia.se (unknown [172.22.191.5]) by s807.loopia.se (Postfix) with ESMTP id 1C734786EEB; Thu, 12 Nov 2026 10:11:53 +0100 (CET) Received: from localhost (unknown [172.22.191.5]) by s980.loopia.se (Postfix) with ESMTP id 1A8EE2201687; Thu, 12 Nov 2026 10:11:53 +0100 (CET) X-Virus-Scanned: amavis at amavis.loopia.se X-Spam-Flag: NO X-Spam-Score: -1.2 X-Spam-Level: X-Spam-Status: No, score=-1.2 tagged_above=-999 required=6.2 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1] autolearn=disabled Authentication-Results: s470.loopia.se (amavis); dkim=pass (2048-bit key) header.d=yesql.se Received: from s979.loopia.se ([172.22.191.5]) by localhost (s470.loopia.se [172.22.190.34]) (amavis, port 10024) with UTF8LMTP id kyztCtWdeUuM; Thu, 12 Nov 2026 10:11:52 +0100 (CET) X-Loopia-Auth: user X-Loopia-User: daniel@yesql.se X-Loopia-Originating-IP: 89.255.232.236 Received: from smtpclient.apple (customer-89-255-232-236.stosn.net [89.255.232.236]) (Authenticated sender: daniel@yesql.se) by s979.loopia.se (Postfix) with ESMTPSA id A2E8710BC545; Thu, 12 Nov 2026 10:11:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yesql.se; s=loopiadkim1707475645; t=1794474712; bh=ITSz3bUxZ/Fu9N7V3rMfJiz6DzpFIcypQezdCXz9hW4=; h=Subject:From:In-Reply-To:Date:Cc:References:To; b=HeS/D/E/iMg1uz1fy0UHxv8MD/M2yk39pZbJyuRBNwg4OMZv5waqztSxMYhjB+sbo WKr688/FfduAlVfQ/gDSGz37L4LOA6kgfdt3rI/O14gT8nekZwXef0DwBWbzdcQ7F2 /Ip/fTlHBd8bNR/VZj2TMVx9UYNdeVPFEZWf/0E6jo+3a5EjucF/ndCx9rkTYyX3lz T0M/fX9yWOWfP+EXtK53tukqU7bMxsWwIye0GuKM9FLEpRNjTUOzHjhPAPV8SC18Kp XlI/uaOA4gxEiYXIJFlbrkdvhNajRjnueyFOQmHl6RAVUcCtJk7n7yQfrr4PAYCs4A sjpDH2MZl8egQ== Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3776.700.51.11.12\)) Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc.. From: Daniel Gustafsson In-Reply-To: Date: Thu, 12 Nov 2026 10:11:42 +0100 Cc: Peter Eisentraut , "David E. Wheeler" , "pgsql-docs@lists.postgresql.org" Content-Transfer-Encoding: 7bit Message-Id: References: <0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com> <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org> To: Karen Jex X-Mailer: Apple Mail (2.3776.700.51.11.12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On 11 Nov 2026, at 16:16, Karen Jex wrote: > I can attempt to split out cleartext and plaintext entries if there's > appetite for that, but I suspect that may actually confuse things > rather than clarifying them. Agreed; we should write the docs for postgres users, knowledge of terminology in cryptography should not be a prerequisite. > Instead, I propose the following glossary > entries to define the way in which we're using the terms: > > plain text > Unformatted, human-readable text that consists of a sequence of > printable characters in a character encoding such as UTF-8. > > cleartext > Unencrypted data; data that exists in an unprotected, readable format > during storage or transmission. Sometimes used as a synonym for > plaintext; the input to an encryption algorithm. Sounds good. I was trying to make the cleartext entry specify that it is generally data which is intended as input to processing, but I wasn't particularly successful in creating anything which reads better than what you have above. -- Daniel Gustafsson