Re: Regex with > 32k different chars causes a backend crash - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Regex with > 32k different chars causes a backend crash
Date
Msg-id 15444.1365003663@sss.pgh.pa.us
Whole thread Raw
In response to Re: Regex with > 32k different chars causes a backend crash  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: Regex with > 32k different chars causes a backend crash
List pgsql-hackers
Heikki Linnakangas <hlinnakangas@vmware.com> writes:
> On 03.04.2013 18:21, Tom Lane wrote:
>> Obviously Henry didn't think that far ahead.  I agree that throwing
>> an error is the best solution, and that widening "color" is probably
>> not what we want to do.  You want to fix that, or shall I?

> I can do it. I assume that Tcl has the same bug, so I'll submit a report 
> there, too.

Yes, definitely.

It occurs to me that at some point it might be useful to convert "color"
to unsigned short, so that you could have 64K of them --- but we'd still
need the error check anyway, and there's no reason to tackle such a
change today.  (This possible change is, however, another reason to not
want pg_trgm looking directly at the internals of the data structure...)
        regards, tom lane



pgsql-hackers by date:

Previous
From: Gavin Flower
Date:
Subject: Re: [PATCH] Exorcise "zero-dimensional" arrays (Was: Re: Should array_length() Return NULL)
Next
From: Jeff Janes
Date:
Subject: Re: commit dfda6ebaec67 versus wal_keep_segments