pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Peter Eisentraut <peter@eisentraut.org>
To: David E. Wheeler <david@justatheory.com>
To: Karen Jex <karenjex@hotmail.com>
Cc: Daniel Gustafsson <daniel@yesql.se>
Cc: pgsql-docs@lists.postgresql.org <pgsql-docs@lists.postgresql.org>
Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc..
Date: Wed, 11 Nov 2026 11:58:48 +0100
Message-ID: <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org> (raw)
In-Reply-To: <0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com>
References: <D7B95A7B-88B8-43E6-9DFB-2261B0849337@yesql.se>
	<DBAP195MB09396FA26617A837F43F7DF3CB762@DBAP195MB0939.EURP195.PROD.OUTLOOK.COM>
	<0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com>

On 06.11.26 15:49, David E. Wheeler wrote:
> On Nov 6, 2026, at 09:44, Karen Jex <karenjex@hotmail.com> wrote:
> 
>> I would love to take this on - thank you for flagging it as a potential first doc-hacking task.
> 
> 
> Yay!
> 
>> Just to confirm my understanding:
>> 1. We should use "cleartext" and "plaintext" throughout, not "clear-text", "clear text", "plain text" or "plain-text".
>> 2. There is at least one case where "plaintext" is used incorrectly in place of "cleartext”.
> 
> I thought these were synonyms, in contrast to “ciphertext”. Should we not pick one to replace all of the others? Searching around a bit, it seems like “ciphertext” and “plaintext” are most often contrasting terms, e.g., https://en.wikipedia.org/wiki/Ciphertext.

My understanding is/was that plaintext is data meant for encryption, 
after which it becomes ciphertext.  Cleartext is data not meant for 
encryption.

So you would use plaintext and ciphertext when describing the steps of 
an encryption method.  And you would use cleartext when describing what 
goes over the wire when you do do LDAP authentication in PostgreSQL.

But it seems like these terms are not actually universally used that 
way.  If we tidy this up, consider adding glossary entries.







view thread (21+ messages)  latest in thread

Message-ID: <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org>
Permalink:  ../72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org/
Also on:    postgresql.org/message-id/72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: peter@eisentraut.org, david@justatheory.com, karenjex@hotmail.com, daniel@yesql.se
  Subject: Re: Good beginner doc-hacking task: clear-text vs. cleartext vs. clear text vs. plaintext etc..
  In-Reply-To: <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org>
  References: <D7B95A7B-88B8-43E6-9DFB-2261B0849337@yesql.se> <DBAP195MB09396FA26617A837F43F7DF3CB762@DBAP195MB0939.EURP195.PROD.OUTLOOK.COM> <0979E710-8C50-4051-87BD-6DE9ABF58938@justatheory.com> <72a2c1fe-5782-463a-a216-7d77eceeac4d@eisentraut.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox