| From: | Jeremy Drake <pgsql(at)jdrake(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pgsql: Fix backend crash in parsing incorrect tsquery. |
| Date: | 2007-02-13 00:13:21 |
| Message-ID: | Pine.BSO.4.64.0702121608250.28908@resin.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
On Tue, 13 Feb 2007, Peter Eisentraut wrote:
> We don't treat crashes to be security issues of the kind that calls for
> the full security exercise.
But if a "security issue", by whatever definition of the term applies to
core, is found in contrib, it would result in the full security exercise,
correct?
Of course, the people I am trying to convince that contrib is not insecure
have yet to update their server with the latest security release (still
running 8.1.3), so it is probably pretty much moot :)
--
Anyone can hold the helm when the sea is calm.
-- Publius Syrus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-13 00:20:22 | Re: pgsql: Fix backend crash in parsing incorrect tsquery. |
| Previous Message | Peter Eisentraut | 2007-02-13 00:02:13 | Re: pgsql: Fix backend crash in parsing incorrect tsquery. |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-02-13 00:20:22 | Re: pgsql: Fix backend crash in parsing incorrect tsquery. |
| Previous Message | Peter Eisentraut | 2007-02-13 00:02:13 | Re: pgsql: Fix backend crash in parsing incorrect tsquery. |