From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | ntufar <ntufar(at)pisem(dot)net>, pgsql-bugs(at)postgresql(dot)org, devrim(at)tdmsoft(dot)com |
Subject: | Re: Turkish downcasting in PL/pgSQL |
Date: | 2004-08-14 15:21:46 |
Message-ID: | 4947.1092496906@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> You'd have to set LC_ALL=C to be really sure to override everything.
> But I would stay away from doing that globally, because all the
> translation work in gcc and make would go to waste.
Agreed. I was toying with changing the FLEX variable to contain
"LC_ALL=C flex" but I'm a bit worried about breaking the build on
some platforms (especially Windows).
> I would also suggest that Nicolai report this issue to the flex
> developers. It's only bound to reappear everywhere case-insensitive
> flex scanners are used.
True. Maybe we should just call it a flex bug and wait for them to
fix it. It's not going to affect builds from tarballs anyway, only
people who build from CVS.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-14 16:03:16 | Re: Turkish downcasting in PL/pgSQL |
Previous Message | Gaetano Mendola | 2004-08-14 11:13:08 | Re: typo in postgresql.conf |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-08-14 15:29:46 | Re: will PITR in 8.0 be usable for "hot spare"/"log shipping" type of replication |
Previous Message | Andrew Dunstan | 2004-08-14 15:09:23 | Re: PITR on Windows? |