Re: BUG #13638: Exception texts from plperl has bad encoding

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: BUG #13638: Exception texts from plperl has bad encoding
Дата
Msg-id 20832.1443213847@sss.pgh.pa.us
обсуждение исходный текст
Ответ на BUG #13638: Exception texts from plperl has bad encoding  (lei@aswsyst.cz)
Список pgsql-bugs
Michal Leinweber <lei@aswsyst.cz> writes:
> The problem is not only with elog call, but it also fires if plpgsql
> code called from plperl function raises exception.

Hmm, yeah, there are a whole bunch of instances of that croak("%s",
edata->message) pattern, and most of them don't have an ancestral SV
to work from.  So we'll need a more general solution anyway, and it
may not be worth changing do_util_elog() to work in a fundamentally
different way than the rest.

            regards, tom lane

В списке pgsql-bugs по дате отправления:

Предыдущее
От: Alvaro Herrera
Дата:
Сообщение: Re: BUG #13638: Exception texts from plperl has bad encoding
Следующее
От: finzelj@gmail.com
Дата:
Сообщение: BUG #13640: Delete isn't using available Index Only Scan