| From: | Hugh Ranalli <hugh(at)whtc(dot)ca> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Ramanarayana <raam(dot)soft(at)gmail(dot)com>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Subject: | Re: Unaccent extension python script Issue in Windows |
| Date: | 2019-03-12 12:30:51 |
| Message-ID: | CAAhbUMOfYCCy0QAJBkCDxRfT59Ri9ubo8+haRxzkJdE52q8ZbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, 11 Mar 2019 at 22:29, Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> On Mon, Mar 11, 2019 at 09:54:45PM +0530, Ramanarayana wrote:
> > I went through the python script and found that the stdout encoding is
> set
> > to utf-8 only if python version is <=2. The same needs to be done for
> > python 3
>
> If you send a patch for that, how would it look like? Could you also
> register any patch produced to the future commit fest? It is here:
> https://commitfest.postgresql.org/23/
We had integrated that into a patch on Bug#15548
(generate_unaccent_rules-remove-combining-diacritical-accents-04.patch),
but there had been issues as overlapping patches had already been
committed. I can try to abstract out these changes in the few days.
Hugh
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2019-03-12 12:38:02 | Re: A separate table level option to control compression |
| Previous Message | Sergei Kornilov | 2019-03-12 12:12:23 | Re: Offline enabling/disabling of data checksums |