| 2007-09-22 01:51:04 |
Christian Reis |
bug |
|
|
added bug |
| 2007-09-22 02:17:44 |
Christian Reis |
launchpad: importance |
Undecided |
Critical |
|
| 2007-09-22 02:17:44 |
Christian Reis |
launchpad: assignee |
|
intellectronica |
|
| 2007-09-24 14:21:37 |
Eleanor Berger |
launchpad: status |
New |
In Progress |
|
| 2007-09-25 15:57:41 |
Christian Reis |
launchpad: importance |
Critical |
Medium |
|
| 2007-09-25 15:57:41 |
Christian Reis |
launchpad: assignee |
intellectronica |
stub |
|
| 2007-09-25 15:59:39 |
Christian Reis |
bug |
|
|
assigned to postgresql (Ubuntu) |
| 2007-09-25 16:01:36 |
Christian Reis |
bug |
|
|
assigned to pgsql |
| 2007-09-27 10:15:57 |
Christian Reis |
description |
Not only do our bugs cause syntax errors in FTI triggers (see bug 141627) they also cause postgresql to SEGV. When issuing an update on all bugs (which triggers FTI triggers to run) as we are doing for today's rollout, at least one bug with an ID between 50,000-100,000 (yay for binary search) causes a cruel crash in the backend. It is reproducible -- James T. triggered it three times today.
NOTICE: A word you are indexing is too long. It will be ignored.
CONTEXT: SQL statement "SELECT setweight(to_tsvector('default', coalesce($1, '')), $2)||setweight(to_tsvector('default', coalesce($3, '')), $4)||setweight(to_tsvector('default', coalesce($5, '')), $6) AS fti"
We need a script which runs through the bugs and tries to update them; running this on carbon will tell us the who the culprits are. Once that is done we can finish issuing the SQL required to add the data that is required to finally fix bug 50663; we have had to roll out without it. |
An update issued to the Launchpad database uncovered a bug in PostgreSQL related to FTI; we were able to crash the backend when issuing a mass-update. We have established a simple testcase that reproduces the problem. |
|
| 2007-09-27 10:15:57 |
Christian Reis |
title |
Updating FTI on one of our bugs causes PostgreSQL to SEGV |
Able to trigger backend segmentation faults via tsearch2 |
|
| 2007-09-27 10:21:45 |
Christian Reis |
pgsql: status |
New |
Fix Committed |
|
| 2007-09-28 12:57:24 |
Martin Pitt |
postgresql-8.2: importance |
Undecided |
Medium |
|
| 2007-09-28 12:57:24 |
Martin Pitt |
postgresql-8.2: assignee |
|
pitti |
|
| 2007-09-28 12:57:24 |
Martin Pitt |
postgresql-8.2: status |
New |
In Progress |
|
| 2007-09-28 13:15:09 |
Martin Pitt |
postgresql-8.2: status |
In Progress |
Fix Released |
|
| 2008-02-01 11:02:23 |
Stuart Bishop |
launchpad: status |
In Progress |
Fix Released |
|
| 2008-12-15 01:06:55 |
Stuart Bishop |
postgresql: status |
Fix Committed |
Fix Released |
|
| 2008-12-15 01:06:55 |
Stuart Bishop |
postgresql: statusexplanation |
Fix committed as per http://archives.postgresql.org/pgsql-bugs/2007-09/msg00138.php |
|
|
| 2008-12-15 02:20:20 |
Hew |
postgresql-8.2: status |
New |
Won't Fix |
|
| 2008-12-15 02:20:20 |
Hew |
postgresql-8.2: statusexplanation |
|
Ubuntu Feisty Fawn is no longer supported, so a SRU will not be issued for this release. Marking Feisty as Won't Fix. |
|
| 2009-08-04 20:26:16 |
Launchpad Janitor |
branch linked |
|
lp:~ubuntu-branches/ubuntu/gutsy/postgresql-8.2/gutsy |
|
| 2009-08-04 20:29:07 |
Launchpad Janitor |
branch linked |
|
lp:ubuntu/intrepid/postgresql-8.2 |
|
| 2012-08-09 23:42:59 |
William Grant |
removed subscriber Launchpad Security |
|
|
|
