Re: The PostgreSQL C Dialect

> On Jun 23, 2026, at 06:53, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
>
> I think the consensus is to prefer "size_t" over "Size" in all-new
> code. But when modifying or adding to existing code, match what's
> around you, which in many places favors "Size".
>
> "Index" is in a grayer area because there was never a solid consensus
> on what to use it for to begin with. Again, there are places where
> the match-nearby-code rule tells you to use Index, but if that doesn't
> apply I'd avoid it.
>
> BTW, you might want to mention match-nearby-code in the para about
> naming too. It's not like we have just one preferred naming style
> --- depending on where you look, there's camelCase, CapitalizeEachWord,
> use_underscores_instead, etc etc. I have no appetite for trying to
> force tree-wide uniformity on that score; but I do get annoyed when
> adjacent routines don't look anything alike.

Thank you! I've updated the page to include statements around this. I took the liberty of borrowing your "camelCase" etc. wording.