BUG #6185: Segmentation fault with NULL string columns - Mailing list pgsql-bugs

From Isaac Jurado
Subject BUG #6185: Segmentation fault with NULL string columns
Date
Msg-id 201108300851.p7U8ptkf014277@wwwmaster.postgresql.org
Whole thread Raw
Responses Re: BUG #6185: Segmentation fault with NULL string columns
Re: BUG #6185: Segmentation fault with NULL string columns
List pgsql-bugs
The following bug has been logged online:

Bug reference:      6185
Logged by:          Isaac Jurado
Email address:      ijurado@econcept.es
PostgreSQL version: 8.4.8
Operating system:   Ubuntu 10.04.03 LTS (x86_64)
Description:        Segmentation fault with NULL string columns
Details:

Here's the script to make it fail:

CREATE DATABASE killme;
\c killme
CREATE FUNCTION to_ascii(bytea, name) RETURNS text AS 'to_ascii_encname'
LANGUAGE internal;
CREATE TABLE mytable (id INTEGER PRIMARY KEY, mytext TEXT);
INSERT INTO mytable (id, mytext) VALUES (1, '');
SELECT * FROM mytable WHERE to_ascii(convert_to(mytext, 'latin1'), 'latin1')
= to_ascii(convert_to('nicetry', 'latin1'), 'latin1');
UPDATE mytable SET mytext=NULL WHERE id=1;
SELECT * FROM mytable WHERE to_ascii(convert_to(mytext, 'latin1'), 'latin1')
= to_ascii(convert_to('nicetry', 'latin1'), 'latin1');

After the second query, the database server segfaults.  Note that it only
fails for NULL values.  The to_ascii/convert_to combination is a recipe for
diacritics elimination found on a PostgreSQL forum.

pgsql-bugs by date:

Previous
From: "Ding Yuan"
Date:
Subject: BUG #6184: Inconsistencies in log messages
Next
From: Heikki Linnakangas
Date:
Subject: Re: BUG #6185: Segmentation fault with NULL string columns