| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Greg Stark <gsstark(at)mit(dot)edu>, Michael Paesold <mpaesold(at)gmx(dot)at>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |
| Date: | 2006-01-09 23:48:34 |
| Message-ID: | 43C2F652.3030901@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
It has probably been sufficiently mitigated on *nix. On Windows, the
choice seems to be between living with the risk and trying my "put the
locales back where they were" patch, which as Tom and Greg point out
might have other consequences. Take your pick.
cheers
andrew
Bruce Momjian wrote:
>Is there a TODO here, even if the Perl folks are supposed to fix it?
>
>---------------------------------------------------------------------------
>
>Andrew Dunstan wrote:
>
>
>>Tom Lane wrote:
>>
>>
>>
>>>>I'm just about out of ideas and right out of time to spend on this.
>>>>
>>>>
>>>>
>>>>
>>>We could just file a Perl bug report and wait for them to fix it.
>>>
>>>
>>>
>>>
>>>
>>>
>>done
>>
>>
>>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2006-01-09 23:49:59 | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |
| Previous Message | Tom Lane | 2006-01-09 23:43:37 | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |