From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Jeff Davis <pgsql(at)j-davis(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Request for comment on setting binary format output per session |
Date: | 2023-04-18 16:23:59 |
Message-ID: | CA+Tgmob1VOjjpkZ+2J9fad8_eU4R0J67esZdD1-8E-gAc4977w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Apr 18, 2023 at 11:51 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> > One thing I think we should do in this area is introduce #defines for
> > all the message type codes and use those instead of having hard-coded
> > constants everywhere.
>
> +1, but I wonder where we should put those exactly. My first thought
> was postgres_ext.h, but the charter for that is
>
> * This file contains declarations of things that are visible everywhere
> * in PostgreSQL *and* are visible to clients of frontend interface libraries.
> * For example, the Oid type is part of the API of libpq and other libraries.
>
> so picayune details of the wire protocol probably don't belong there.
> Maybe we need a new header concerned with the wire protocol?
Yeah. I sort of thought maybe one of the files in src/include/libpq
would be the right place, but it doesn't look like it.
--
Robert Haas
EDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2023-04-18 16:24:11 | Re: constants for tar header offsets |
Previous Message | Nikita Malakhov | 2023-04-18 16:12:08 | Re: [PATCH] Compression dictionaries for JSONB |