"Andreas Pflug" <[EMAIL PROTECTED]> 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

Reply via email to