From: | Peter Smith <smithpb2250(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | TOAST versus toast |
Date: | 2025-01-16 03:57:49 |
Message-ID: | CAHut+PtxXLJFhwJFvx+M=Ux8WGHU85XbT3nDqk-aAUS3E5ANCw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi,
During some recent reviews, I came across some comments mentioning "toast" ...
TOAST is a PostgreSQL acronym for "The Oversized-Attribute Storage
Technique" [1].
But, toast is just toast [2].
~
AFAIK it is usual practice to uppercase acronyms to distinguish them
from ordinary words, but PostgreSQL currently has a scattered mixture
of "TOAST" versus "toast". Usage seems about 50:50.
Now that I have seen the problem I can't unsee it, and it is
everywhere, so here is a patch to address all the lowercase toast in
the documentation.
Note, for the unusual cases I have used the same wording as per the
original TOAST page [1], so:
- "toasted" becomes "TOASTed".
- "toastable" becomes "TOAST-able"
- "untoasted" becomes "un-TOASTed"
- "detoasted" is unchanged (and so is "detoast")
~~~
There are many more "toast" examples found in the source code
comments, but I'll first wait to see if this patch is accepted before
looking to address those.
======
[1] TOAST -- https://www.postgresql.org/docs/current/storage-toast.html
[2] toast -- https://en.wikipedia.org/wiki/Toast_(food)
Kind Regards,
Peter Smith.
Fujitsu Australia
Attachment | Content-Type | Size |
---|---|---|
v1-0001-TOAST-not-toast.patch | application/octet-stream | 12.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2025-01-16 04:14:31 | Re: Make pg_stat_io view count IOs as bytes instead of blocks |
Previous Message | Tom Lane | 2025-01-16 02:59:59 | Re: pg_dumpall appendPQExpBuffer construct sql need an white space |