=?gb18030?B?u9i4tKO6IFtCVUdTXSBCVUcgIzEzNzYyOiBzZXJ2?= =?gb18030?B?ZXIgd2lsbCBjcmFzaCBhZnRlciBzdXBlcnVzZXIg?= =?gb18030?B?YWx0ZXIgZnVuY3Rpb24gYW5kIHNldCBjbGllbnRf?= =?gb18030?B?ZW5jb2Rpbmc=?= - Mailing list pgsql-bugs

From 笑见江湖
Subject =?gb18030?B?u9i4tKO6IFtCVUdTXSBCVUcgIzEzNzYyOiBzZXJ2?= =?gb18030?B?ZXIgd2lsbCBjcmFzaCBhZnRlciBzdXBlcnVzZXIg?= =?gb18030?B?YWx0ZXIgZnVuY3Rpb24gYW5kIHNldCBjbGllbnRf?= =?gb18030?B?ZW5jb2Rpbmc=?=
Date
Msg-id tencent_5C106B6934A0F0A048A28456@qq.com
Whole thread Raw
In response to Re: BUG #13762: server will crash after superuser alter function and set client_encoding  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] 回复: [BUGS] BUG #13762: server will crash after superuser alter function and set client_encoding  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-bugs
Although its is in the category of "don't do that",  but server crashed is dangerous. If I alter a function to "set work_mem = '4MB'", it should be no problem and reasonable.

Sorry, the correct statements which make server crash is:
 
1. alter function koi8r_to_utf8(integer, integer, cstring, internal, integer) set work_mem = '4MB';
2. set client_encoding = 'koi8';
3. select 1;


------------------ 原始邮件 ------------------
发件人: "Tom Lane";<tgl@sss.pgh.pa.us>;
发送时间: 2015年11月9日(星期一) 晚上10:45
收件人: "笑见江湖"<funnyxj@qq.com>;
抄送: "pgsql-bugs"<pgsql-bugs@postgresql.org>;
主题: Re: [BUGS] BUG #13762: server will crash after superuser alter function and set client_encoding

funnyxj@qq.com writes:
> When superuser execute the following statements, the server will crash, it
> may be a bug.

> 1. alter function koi8r_to_utf8(integer, integer, cstring, internal,
> integer) set work_mem = default ;

That would be in the category of "don't do that".  Encoding conversion
functions are invoked using special code paths that don't support every
possible option for functions, so I'm not too surprised that this breaks
things (and I see no reason to expend effort to try to make it not be
broken).

FWIW, I can't reproduce a crash with the described case either, so
I think there's probably some additional condition required.  But
it doesn't really matter.  Mucking with the properties of built-in
functions isn't considered a supported thing to do.

regards, tom lane


--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: "笑见江湖"
Date:
Subject: =?gb18030?B?u9i4tKO6IFtCVUdTXSBCVUcgIzEzNzYyOiBzZXJ2?= =?gb18030?B?ZXIgd2lsbCBjcmFzaCBhZnRlciBzdXBlcnVzZXIg?= =?gb18030?B?YWx0ZXJmdW5jdGlvbiBhbmQgc2V0IGNsaWVudF9l?= =?gb18030?B?bmNvZGluZw==?=
Next
From: Michael Paquier
Date:
Subject: Re: [BUGS] 回复: [BUGS] BUG #13762: server will crash after superuser alter function and set client_encoding