| From: | John Naylor <johncnaylorls(at)gmail(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: The PostgreSQL C Dialect |
| Date: | 2026-06-23 03:32:49 |
| Message-ID: | CANWCAZZJxgDAUsBK-1CctczwTz2TVo3TzjhhSD7fAA9EWte3eA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 23, 2026 at 2:39 AM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
> When I was writing my first PostgreSQL extension, I was at sea on a lot of the conventions that make up the "PostgreSQL C Dialect." I've taken my notes, added some additional things that confused me, and put it up on the wiki for review:
>
> https://wiki.postgresql.org/wiki/The_PostgreSQL_C_Dialect
>
> Feedback welcome, of course!
Cool work! Minor comments:
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.
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.
--
John Naylor
Amazon Web Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bertrand Drouvot | 2026-06-23 03:53:34 | Re: The PostgreSQL C Dialect |
| Previous Message | Japin Li | 2026-06-23 03:17:31 | Re: md5_password_warnings for password auth with MD5-encrypted passwords |