| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |
| Date: | 2005-12-28 17:23:59 |
| Message-ID: | 44947.68.143.134.146.1135790639.squirrel@www.dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane said:
> I wrote:
>> So the mere act of defining a plperl function, even with
>> check_function_bodies = false, is sufficient to send control through
>> that bit of libperl code that does setlocale(LC_ALL, ""). Ugh.
>> This is much worse than I thought.
>
> It seems one ingredient in this is that the plperl function validator
> fails to honor check_function_bodies, and hence is calling libperl
> anyway. I wonder if that explains the sudden rise in incidents in 8.1?
>
That's probably because I was unaware of its existence.
It should certainly be fixed, but surely at best this would only delay
seeing the ugly locale effect - as soon as you call a perl function you'll
be back in the same boat regardless.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2005-12-28 17:33:33 | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |
| Previous Message | Tom Lane | 2005-12-28 17:13:08 | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |