Bug #479: Backend crashes when using certain commands with SJIS encoded databases

Anonymous (null(at)null(dot)null) reports a bug with a severity of 2
The lower the number the more severe it is.

Short Description
Backend crashes when using certain commands with SJIS encoded databases

Long Description
The problem seems to occur when using databases with SJIS encoding.

So far, I have discovered that using the LIKE operator in a SELECT query, as well as any of the \d (describe) functions in psql causes the backend to restart without returning any data.

I have tested this on several versions of PostgreSQL on several machines (all running Linux of some version or another) and I get the same result on all of them.

Sample Code
Here's a quick test I performed on an example database using the LIKE operator in a SELECT query in psql:

carfare=# select * from costdata where data1 like 'test';
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: Failed.

!# \c carfare
No Postgres username specified in startup packet.
Segmentation fault (core dumped)

Here's the backend's log for that period:

Server process (pid 1506) exited with status 139 at Fri Oct 12 10:45:33 2001
Terminating any active server processes...
Server processes were terminated at Fri Oct 12 10:45:33 2001
Reinitializing shared memory and semaphores
011012.10:45:33.303 [1507] DEBUG: Data Base System is starting up at Fri Oct 12 10:45:33 2001
011012.10:45:33.304 [1507] DEBUG: Data Base System was interrupted being in production at Fri Oct 12 10:39:07 2001
011012.10:45:33.306 [1507] DEBUG: Data Base System is in production state at Fri Oct 12 10:45:33 2001

No file was uploaded with this report