| From: | "David E(dot) Wheeler" <david(at)kineticode(dot)com> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: PATCH: CITEXT 2.0 v3 |
| Date: | 2008-07-14 17:57:34 |
| Message-ID: | E778558F-21CA-4E58-BF94-215448DB09E3@kineticode.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jul 14, 2008, at 10:55, Andrew Dunstan wrote:
> No.
>
> --no-locale is the same as --locale=C which means the encoding is
> SQL_ASCII.
I've used --no-locale --encoding UTF-8 many times. But if the
regressions run with SQL_ASCII…well, I'm just amazed that there
haven't been more unexpected side-effects to source code changes
without controlling for such variables in tests. Seems like a lot to
keep in one's head.
Anyway, are tests for contrib modules run on the build farms? If so, I
could still potentially get around this issue by turning off ECHO.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-07-14 17:58:35 | Re: PATCH: CITEXT 2.0 v3 |
| Previous Message | Andrew Dunstan | 2008-07-14 17:55:07 | Re: PATCH: CITEXT 2.0 v3 |