Re: The PostgreSQL C Dialect

From: Christophe Pettus <xof(at)thebuild(dot)com>
To: John Naylor <johncnaylorls(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: The PostgreSQL C Dialect
Date: 2026-06-23 06:42:37
Message-ID: ACE262A9-0CC4-4622-8DE0-1B0F2BD26D84@thebuild.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Jun 22, 2026, at 20:32, John Naylor <johncnaylorls(at)gmail(dot)com> wrote:
>
> Size, Index - These are not common, and I think they are actually
> discouraged now, in favor of the more common size_t and uint32. I'm
> not sure if there's a consensus on that, though.

Thanks! I'll be happy to edit if appropriate.

> C99 -> we started requiring C11 during the dev cycle of the PG19, and
> it doesn't seem to early to mention that. The part about C99 features
> we don't allow are still accurate, I believe.

Good catch. I've updated the mentions, as well as moving the C-language baseline up (it was in kind of a weird and offhand place before). I did add an admonition to not be too innovative in the use of new features in C11 without making sure there is consensus here as to their use.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Chengpeng Yan 2026-06-23 06:46:35 Re: Add a greedy join search algorithm to handle large join problems
Previous Message Michael Paquier 2026-06-23 06:42:02 Re: [PATCH] doc: clarify pg_stat_lock.fastpath_exceeded scope