Re: Request for comment on setting binary format output per session
Peter Eisentraut <peter@eisentraut.org>
From: Peter Eisentraut <peter@eisentraut.org>
To: Dave Cramer <davecramer@gmail.com>
Cc: Merlin Moncure <mmoncure@gmail.com>, Robert Haas <robertmhaas@gmail.com>,
Tom Lane <tgl@sss.pgh.pa.us>, Jeff Davis <pgsql@j-davis.com>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-10-06T11:11:24Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Silence compiler warning introduced in 1edb3b491b
- fba2112b1569 17.0 cited
On 04.10.23 20:30, Dave Cramer wrote: > We need to > figure out what is the right way to globally identify types, like > either > by fully-qualified name, by base name, some combination, how does it > work with extensions, or do we need a new mechanism like UUIDs. I > think > that is something we need to work out, no matter which protocol > mechanism we end up using. > > > So how is this different than the GUC that I proposed ? The last patch I see from you in this thread uses OIDs, which I have argued is not the right solution.