Author: Sergiy VyshnevetskiySergiy Vyshnevetskiy Date: Oct 12, 2006 12:51
This message is in MIME format. The first part should be readable text,
while the remaining parts are likely unreadable without MIME-aware tools.
--1297089064-1899461714-1160682627=:28687
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
On Tue, 10 Oct 2006, Tom Lane wrote:
> Sergiy Vyshnevetskiy vostok.net> writes:>> Here is a new and improved patch, that closes security hole as well.
>
> We really can't consider a patch like this, because not only does it
> ignore the problem of multiple spellings of encoding names, but it
> actually breaks existing functionality on platforms with a variant
> spelling of the name. I think a minimum requirement ought to be that
> it work with any of the spellings recognized by initdb.
Alright, that was too strict. But when server uses messages in
LC_CTYPE encoding with data in database encoding and pushes this mix
through database-to-client charset conversion - that's a bug. PostgreSQL
bug. And "UTF-8 panic" is it's direct result.
| 
