Group: pgsql.bugs


Subject: BUG #3716: utf8 crash with replace
From: pgadmin@pse-consulting.de ("Andreas Pflug")
Date: 11/2/2007 8:00:59 PM
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') ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match

Subject: BUG #3716: utf8 crash with replace
From: tgl@sss.pgh.pa.us (Tom Lane)
Date: 11/3/2007 9:54:50 PM
"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 ---------------------------(end of broadcast)--------------------------- TIP 2: Don't 'kill -9' the postmaster