Re: Collation version tracking for macOS
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Jeff Davis <pgsql@j-davis.com>
Cc: vignesh C <vignesh21@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Joe Conway <mail@joeconway.com>,
Peter Eisentraut <peter.eisentraut@enterprisedb.com>, Jeremy Schneider <schneider@ardentperf.com>, Peter Geoghegan <pg@bowt.ie>,
"Nasby, Jim" <nasbyj@amazon.com>, Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2024-02-01T20:58:01Z
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 →
-
Fix copy&paste typo in comment
- 402388946fb3 17.0 cited
On Sun, Jan 21, 2024 at 1:58 PM Jeff Davis <pgsql@j-davis.com> wrote: > I rendered the docs I wrote as an HTML page and attached it to this > thread, to make it easier for others to read and comment. It's > basically a tool for experts who are willing to devote effort to > managing their collations and ICU libraries. Is that what we want? > > At an implementation level, did I get the extension APIs right? I > considered making the API simpler, but that would require the extension > to do quite a bit more work (including a lot of redundant work) to use > ICU properly. Not that I'm the most qualified person to have an opinion on this topic, but did you intend to attach this stuff to this email, or is it somewhere else? -- Robert Haas EDB: http://www.enterprisedb.com