Re: TOAST versus toast

2025-04-13 Thread wenhui qiu
Hi, I think this point is of no significance at all. Besides, this is a document that has been around for over ten years. Everyone has become accustomed to this kind of expression. This is just a case of being full but having nothing to do with anything. On Sat, 12 Apr 2025 at 10:31, David G. Joh

Re: TOAST versus toast

2025-04-11 Thread David G. Johnston
On Sun, Mar 16, 2025 at 8:33 PM Peter Smith wrote: > Thanks for your suggestions. At this point option (1) is looking most > attractive. Probably, I will just withdraw the CF entry soon unless > there is some new interest. Just chipping away fixing a few places > isn't going to achieve the consis

Re: TOAST versus toast

2025-03-20 Thread Álvaro Herrera
> On 3/17/25 00:24, Tom Lane wrote: > > Note the lack of any upper case. Shortly later we reverse-engineered > > an acronym for it [2], with the winner being Tom Lockhart's > > > > The Oversized-Attribute Storage Technique I (very easily) found a reference to the GSM tool: https://linux.die

Re: TOAST versus toast

2025-03-17 Thread Jan Wieck
On 3/17/25 00:24, Tom Lane wrote: Note the lack of any upper case. Shortly later we reverse-engineered an acronym for it [2], with the winner being Tom Lockhart's The Oversized-Attribute Storage Technique Which made it into an acronym. Acronyms are typically capitalized to distinguish t

Re: TOAST versus toast

2025-03-16 Thread Tom Lane
Jan Wieck writes: > As the original author of the TOAST I vote for TOAST being used as the > name/acronym of the feature, but toast in all other cases like as verb. Well, if we're appealing to history ... I dug in the archives and found that you seem to have invented the name here [1]: Sinc

Re: TOAST versus toast

2025-03-16 Thread Isaac Morland
On Sun, 16 Mar 2025 at 19:38, Peter Smith wrote: > But, because of all the differing views expressed here I'm not sure > now how to proceed. Any ideas? > May I suggest that you start with a patch to Appendix J, section 6 to codify whatever is decided? https://www.postgresql.org/docs/current/do

Re: TOAST versus toast

2025-03-16 Thread Jan Wieck
As the original author of the TOAST I vote for TOAST being used as the name/acronym of the feature, but toast in all other cases like as verb. Best Regards, Jan On 3/16/25 22:49, Robert Haas wrote: On Sun, Mar 16, 2025 at 7:38 PM Peter Smith wrote: If I understand correctly, the summary is

Re: TOAST versus toast

2025-03-16 Thread Peter Smith
On Mon, Mar 17, 2025 at 1:50 PM Robert Haas wrote: > > On Sun, Mar 16, 2025 at 7:38 PM Peter Smith wrote: > > If I understand correctly, the summary is: > > - Tom: +1 for "TOAST table", but changing all the combined forms is > > maybe not worth the effort. > > - DavidJ: Wants to uppercase TOAST

Re: TOAST versus toast

2025-03-16 Thread Robert Haas
On Sun, Mar 16, 2025 at 7:38 PM Peter Smith wrote: > If I understand correctly, the summary is: > - Tom: +1 for "TOAST table", but changing all the combined forms is > maybe not worth the effort. > - DavidJ: Wants to uppercase TOAST only when it refers to 'technique'; > lowercase otherwise. > - R

Re: TOAST versus toast

2025-03-16 Thread Peter Smith
Hi, If I understand correctly, the summary is: - Tom: +1 for "TOAST table", but changing all the combined forms is maybe not worth the effort. - DavidJ: Wants to uppercase TOAST only when it refers to 'technique'; lowercase otherwise. - RobertT: The verbs should be lowercase (e.g. laser). Each-wa

Re: TOAST versus toast

2025-03-07 Thread Robert Haas
On Fri, Mar 7, 2025 at 11:24 AM Robert Treat wrote: > everyday english/grammar; as an example, people would generally write > "the dr. lasered the tumor" not "the dr. LASERed the tumor". For the record, I wouldn't write either of those things if I wanted to be certain of being understood. Using a

Re: TOAST versus toast

2025-03-07 Thread Robert Treat
On Mon, Feb 17, 2025 at 6:27 PM David G. Johnston wrote: > > On Wed, Jan 15, 2025 at 10:38 PM Peter Smith wrote: >> >> On Thu, Jan 16, 2025 at 3:26 PM Tom Lane wrote: >> > >> > Peter Smith writes: >> > > During some recent reviews, I came across some comments mentioning >> > > "toast" ... >> >

Re: TOAST versus toast

2025-02-17 Thread David G. Johnston
On Wed, Jan 15, 2025 at 10:38 PM Peter Smith wrote: > On Thu, Jan 16, 2025 at 3:26 PM Tom Lane wrote: > > > > Peter Smith writes: > > > During some recent reviews, I came across some comments mentioning > "toast" ... > > > TOAST is a PostgreSQL acronym for "The Oversized-Attribute Storage > > >

Re: TOAST versus toast

2025-01-15 Thread Peter Smith
On Thu, Jan 16, 2025 at 3:26 PM Tom Lane wrote: > > Peter Smith 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 a

Re: TOAST versus toast

2025-01-15 Thread Tom Lane
Peter Smith 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 questio

TOAST versus toast

2025-01-15 Thread Peter Smith
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. Not