| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Request for comment on setting binary format output per session |
| Date: | 2023-03-22 09:21:17 |
| Message-ID: | 39e252a1-2766-e543-c01d-0e4fdbdf7456@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 20.03.23 18:04, Jeff Davis wrote:
> Also, if we're going to make the binary format more practical to use,
> can we document the expectations better? It seems the expecatation is
> that the binary format just never changes, and that if it does, that's
> a new type name.
I've been thinking that we need some new kind of identifier to allow
clients to process types in more sophisticated ways.
For example, each type could be (self-)assigned a UUID, which is fixed
for that type no matter in which schema or under what extension name or
with what OID it is installed. Client libraries could then hardcode
that UUID for processing the types. Conversely, the UUID could be
changed if the wire format of the type is changed, without having to
change the type name.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-03-22 09:28:01 | Re: Can we avoid chdir'ing in resolve_symlinks() ? |
| Previous Message | Peter Eisentraut | 2023-03-22 09:14:28 | Re: Request for comment on setting binary format output per session |