BUG #3716: utf8 crash with replace

Started by Andreas Pflugover 18 years ago3 messagesbugs
Jump to latest
#1Andreas Pflug
pgadmin@pse-consulting.de

The following bug has been logged online:

Bug reference: 3716
Logged by: Andreas Pflug
Email address: pgadmin@pse-consulting.de
PostgreSQL version: 8.2.4
Operating system: Linux,Windows
Description: utf8 crash with replace
Details:

If replace is used with UTF8 client_encoding, searching for a malformed
string, the backend will crash.

SELECT replace('Ärger', chr(195), 'Ae')

#2Tom Lane
tgl@sss.pgh.pa.us
In reply to: Andreas Pflug (#1)
Re: BUG #3716: utf8 crash with replace

"Andreas Pflug" <pgadmin@pse-consulting.de> writes:

If replace is used with UTF8 client_encoding, searching for a malformed
string, the backend will crash.

SELECT replace('Ärger', chr(195), 'Ae')

I see no crash here. Maybe it's been fixed since 8.2.4? Please try
8.2.5. If you still get a crash, could you send a stack trace?

regards, tom lane

#3Andreas Pflug
pgadmin@pse-consulting.de
In reply to: Tom Lane (#2)
Re: BUG #3716: utf8 crash with replace

Tom Lane wrote:

"Andreas Pflug" <pgadmin@pse-consulting.de> writes:

If replace is used with UTF8 client_encoding, searching for a malformed
string, the backend will crash.

SELECT replace('Ärger', chr(195), 'Ae')

I see no crash here. Maybe it's been fixed since 8.2.4? Please try
8.2.5. If you still get a crash, could you send a stack trace?

Ok, apparently fixed in 8.2.5.

Regards,
Andreas