From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
---|---|
To: | Peter Smith <smithpb2250(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: TOAST versus toast |
Date: | 2025-07-01 08:29:29 |
Message-ID: | 96f62e7c-c3a2-41d9-9d13-5bda416475a5@eisentraut.org |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 16.01.25 06:38, Peter Smith wrote:
> On Thu, Jan 16, 2025 at 3:26 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>> Peter Smith <smithpb2250(at)gmail(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2025-07-01 08:31:38 | Re: C11 / VS 2019 |
Previous Message | Jelte Fennema-Nio | 2025-07-01 08:14:56 | Re: BackendKeyData is mandatory? |