| From: | Jelte Fennema-Nio <postgres(at)jeltef(dot)nl> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | Jacob Champion <jacob(dot)champion(at)enterprisedb(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Robert Haas <robertmhaas(at)gmail(dot)com> |
| Subject: | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta |
| Date: | 2026-01-31 11:13:36 |
| Message-ID: | CAGECzQQHJkzssOfkHDzQny9_s4cck=8-ecG2JELS0jVCd1fTiA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 30 Jan 2026 at 20:14, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> Definite screenshot-2 preference for me. Though I do wonder just looking at the image whether the reserved stuff even needs a table. The first row is not even a parameter but a guideline, and the second pertains to testing which seems like it can be incorporated separately. I'd either go for just one table or two separate tables but not the combined variant in screenshot-1. I'm not seeing an advantage to be gained by the integration.
Agreed. I expect maybe we'll reserve more protocol extensions in the
future (either the improved grease, or when we'll stop supporting an
extension at some point).
Regarding _pq_.[name], I agree with David that I think it would be
better to make that part of the introductory paragraph.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrei Lepikhov | 2026-01-31 11:18:43 | Re: Is there value in having optimizer stats for joins/foreignkeys? |
| Previous Message | Jelte Fennema-Nio | 2026-01-31 11:06:41 | Re: libpq: Bump protocol version to version 3.2 at least until the first/second beta |