Horton

Re: TOAST versus toast

Peter Eisentraut <peter@eisentraut.org>

View thread
From: Peter Eisentraut <peter@eisentraut.org>
To: Peter Smith <smithpb2250@gmail.com>, Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-07-01T08:29:29Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. doc: TOAST not toast

On 16.01.25 06:38, Peter Smith wrote:
> On Thu, Jan 16, 2025 at 3:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>
>> Peter Smith <smithpb2250@gmail.com> writes:
>>> During some recent reviews, I came across some comments mentioning "toast" ...
>>> TOAST is a PostgreSQL acronym for "The Oversized-Attribute Storage
>>> Technique" [1].
>>
>> It is indeed an acronym, but usages such as "toasting" are all over
>> our code and docs, as you see.  I question whether changing that
>> to "TOASTing" improves readability.  I agree that consistently
>> saying "TOAST table" not "toast table" is a good idea, but I'm
>> not quite convinced that removing every last lower-case occurrence
>> is a win, especially in these combined forms.
>>
> 
> Hi, thanks for the reply.
> 
> How about I reduce the scope by only tackling the uncontroversial
> stuff, and leave all those "combined forms" for another day?
> 
> Attached is the reduced patch for changes to the documentation.

committed