Skip site navigation (1) Skip section navigation (2)

BUG #6185: Segmentation fault with NULL string columns

From: "Isaac Jurado" <ijurado(at)econcept(dot)es>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #6185: Segmentation fault with NULL string columns
Date: 2011-08-30 08:51:55
Message-ID: 201108300851.p7U8ptkf014277@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      6185
Logged by:          Isaac Jurado
Email address:      ijurado(at)econcept(dot)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.

Responses

pgsql-bugs by date

Next:From: LampaDate: 2011-08-30 11:20:20
Subject: BUG #6186: out of memory while analyze
Previous:From: Ding YuanDate: 2011-08-30 07:15:19
Subject: BUG #6184: Inconsistencies in log messages

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group