Re: TOAST versus toast
Isaac Morland <isaac.morland@gmail.com>
From: Isaac Morland <isaac.morland@gmail.com>
To: Peter Smith <smithpb2250@gmail.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-03-17T03:31:13Z
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 →
-
doc: TOAST not toast
- 83389838827b 19 (unreleased) landed
On Sun, 16 Mar 2025 at 19:38, Peter Smith <smithpb2250@gmail.com> 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/docguide-style.html This is made a bit awkward because right now the style guide only has one subsection, relating to reference page organization. So essentially I'm suggesting an entirely new subsection which could eventually cover things like capitalization and which grammatical forms to prefer, and that you start with the toast/TOAST rules. Once you have at least one rule agreed and added to the style guide, then a patch to revise existing examples of contrary usage would be in my opinion a more clear win than it is now. The above makes more sense to me if there are other questions of this general nature that could benefit from an explicit mention in a style guide, even if this patch wouldn't do that. If this is the only question like this, then it looks a bit weird to add a whole section just for it. But I lean towards the idea that over time there might be a number of decisions of this nature that ought to be made and followed consistently.