Re: daitch_mokotoff module

Tom Lane <tgl@sss.pgh.pa.us>

From: Tom Lane <tgl@sss.pgh.pa.us>

To: Dag Lem <dag@nimrod.no>

Cc: Andrew Dunstan <andrew@dunslane.net>, Tomas Vondra <tomas.vondra@enterprisedb.com>, Andres Freund <andres@anarazel.de>, Alvaro Herrera <alvherre@alvh.no-ip.org>, Paul Ramsey <pramsey@cleverelephant.ca>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2023-04-08T03:25:32Z

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 →

Avoid using non-ASCII commentary in daitch_mokotoff.c.
- 1c54b93a8cf9 16.0 landed
Remove some non-ASCII symbols from a comment.
- d6b5dee42de7 16.0 landed
Remove useless dependencies in daitch_mokotoff_header.pl.
- 2bfbad9c4220 16.0 landed
Pacify perlcritic.
- edc627ae2763 16.0 landed
Add support for Daitch-Mokotoff Soundex in contrib/fuzzystrmatch.
- a290378a3752 16.0 landed
Enable routine running of citext's UTF8-specific test cases.
- c2e8bd27519f 15.0 landed

I wrote:
> Anyway, I assume this is just syntactic sugar for something
> we can do another way?  If it's at all fundamental, I'll have
> to back the patch out.

On closer inspection, this script is completely devoid of any
need to deal in non-ASCII data at all.  So I just nuked the
"use" lines.

			regards, tom lane