Re: pgsql: Fix backend crash in parsing incorrect tsquery. - Mailing list pgsql-hackers

From Jeremy Drake
Subject Re: pgsql: Fix backend crash in parsing incorrect tsquery.
Date
Msg-id Pine.BSO.4.64.0702121522380.28908@resin.csoft.net
Whole thread Raw
Responses Re: pgsql: Fix backend crash in parsing incorrect tsquery.  (Peter Eisentraut <peter_e@gmx.net>)
Re: pgsql: Fix backend crash in parsing incorrect tsquery.  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, 12 Feb 2007, Teodor Sigaev wrote:

> Log Message:
> -----------
> Fix backend crash in parsing incorrect tsquery.
>
> Per report from Jon Rosebaugh <jon@inklesspen.com>

Is this a security issue?  Does it need a new security release?  I hope
that the answer is not "this is contrib, it isn't as important" since I
have been trying to convince others that contrib is not less secure or
well supported than core.  If this is a security issue (and if it can
crash the backend due to a function parameter, it probably is) the
community response to it will be particularly compelling evidence.

> Modified Files:
> --------------
>     pgsql/contrib/tsearch2:
>         query.c (r1.30 -> r1.31)
>         (http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/tsearch2/query.c.diff?r1=1.30&r2=1.31)
>
>

-- 
Colvard's Logical Premises:All probabilities are 50%.  Either a thing will happen or itwon't.

Colvard's Unconscionable Commentary:This is especially true when dealing with someone you'reattracted to.

Grelb's CommentaryLikelihoods, however, are 90% against you.


pgsql-hackers by date:

Previous
From: Tatsuo Ishii
Date:
Subject: Re: tsearch2: enable non ascii stop words with C locale
Next
From: Peter Eisentraut
Date:
Subject: Re: XML export function signatures