| From: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com> |
|---|---|
| To: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Nathan Bossart <nathandbossart(at)gmail(dot)com> |
| Subject: | Re: [PATCH] Reorganize pqcomm.h a bit |
| Date: | 2025-11-22 00:25:11 |
| Message-ID: | CAOYmi+mkeGkvOGe7M5oOtRxJyAMiSqm4ZDzg+qRVHYSvTBhuKQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Nov 21, 2025 at 2:01 PM Jacob Champion
<jacob(dot)champion(at)enterprisedb(dot)com> wrote:
> Good point. I think "actual protocol version" might get a little
> confusing for a casual reader if/when your _GREASE macro arrives,
> though. I'll do some wordsmithing.
Actually, maybe brevity is best, as in v2? They're reserved, they're
special; readers can look at the comment for the reservation in
question to find out why, and then we don't have to generalize in the
section header.
--Jacob
| Attachment | Content-Type | Size |
|---|---|---|
| v2-0001-Reorganize-pqcomm.h-a-bit.patch | application/octet-stream | 4.3 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nikolay Samokhvalov | 2025-11-22 00:43:31 | Missing wait events (gap analysis) |
| Previous Message | Tom Lane | 2025-11-22 00:01:24 | Re: Add notification on BEGIN ATOMIC SQL functions using temp relations |