Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: 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 20:29:52
Message-ID: 1136838592.3064.6.camel@swithin
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 2006-01-09 at 12:06 -0500, Tom Lane wrote:
> Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> > I don't know. Reading that code just makes my head spin ...
>
> Yeah, too many ifdefs :-(. But I suppose that the initial
> "#ifdef LOCALE_ENVIRON_REQUIRED" block is not compiled on sane
> platforms, meaning that the first code in the routine is the
> unconditional
> if (! setlocale(LC_ALL, ""))
> setlocale_failure = TRUE;
>

*doh!* I had misread that. Now I see.

On Windows that pretty much gives the game away.

>
> > 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.
>

What's the data risk?

cheers

andrew

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-01-09 21:23:35 Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
Previous Message Tom Lane 2006-01-09 19:51:52 Re: lookup_rowtype_tupdesc considered harmful