Re: chr() is still too loose about UTF8 code points

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: chr() is still too loose about UTF8 code points
Дата
Msg-id 19277.1400266387@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: chr() is still too loose about UTF8 code points  (David G Johnston <david.g.johnston@gmail.com>)
Список pgsql-hackers
David G Johnston <david.g.johnston@gmail.com> writes:
> Tom Lane-2 wrote
>> While I'd be willing to ignore that risk so far as code points above
>> 10ffff go, if we want pg_utf8_islegal to be happy then we will also
>> have to reject surrogate-pair code points.  It's not beyond the realm
>> of possibility that somebody is intentionally generating such code
>> points with chr(), despite the dump/reload hazard.  So now I agree
>> that this is sounding more like a major-version-only behavioral change.

> I would tend to agree on principle - though since this does fall in a
> grey-area does 9.4 qualify for this bug-fix.

I don't think it's too late to change this in 9.4.  The discussion was
about whether to back-patch.
        regards, tom lane



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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: %d in log_line_prefix doesn't work for bg/autovacuum workers
Следующее
От: Andres Freund
Дата:
Сообщение: Re: %d in log_line_prefix doesn't work for bg/autovacuum workers