Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
От | Andrew Dunstan |
---|---|
Тема | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) |
Дата | |
Msg-id | 44947.68.143.134.146.1135790639.squirrel@www.dunslane.net обсуждение исходный текст |
Ответ на | Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: plperl vs LC_COLLATE (was Re: Possible savepoint bug)
|
Список | 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
В списке pgsql-hackers по дате отправления: