Segmentation fault with 8.3 FTS ISpell

From: Hannes Dorbath <light(at)theendofthetunnel(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Segmentation fault with 8.3 FTS ISpell
Date: 2008-01-15 11:04:34
Message-ID: fmi409$7t2$1@news.hub.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Crash happens about 7 minutes after issuing the UPDATE statement with
current CVS HEAD. The table has around 5 million rows. It's always
reproducible.

ISpell dict used:
http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/dicts/ispell/ispell-german-compound.tar.gz
(iconved to UTF-8)

Welcome to psql 8.3RC1, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

test=# \dFd+ german_ispell
List of text search
dictionaries
Schema | Name | Template |
Init options | Description
--------+---------------+-------------------+---------------------------------------------------------------+-------------
public | german_ispell | pg_catalog.ispell | dictfile = 'german',
afffile = 'german', stopwords = 'german' |
(1 row)

test=# \dF+ german_ispell
Text search configuration "pg_catalog.german_ispell"
Parser: "pg_catalog.default"
Token | Dictionaries
-----------------+---------------------------
asciihword | german_ispell,german_stem
asciiword | german_ispell,german_stem
email | simple
file | simple
float | simple
host | simple
hword | german_ispell,german_stem
hword_asciipart | german_ispell,german_stem
hword_numpart | simple
hword_part | german_ispell,german_stem
int | simple
numhword | simple
numword | simple
sfloat | simple
uint | simple
url | simple
url_path | simple
version | simple
word | german_ispell,german_stem

test=# SELECT ts_debug('autofahren');
ts_debug
-----------------------------------------------------------------------------------------------------------------
(asciiword,"Word, all
ASCII",autofahren,"{german_ispell,german_stem}",german_ispell,"{autofahren,auto,fahren}")
(1 row)

test=# \d+ test
Table "public.test"
Column | Type | Modifiers
| Description
--------+----------+---------------------------------------------------+-------------
id | integer | not null default nextval('test_id_seq'::regclass) |
text | text | not null |
tsv | tsvector | |
Indexes:
"test_pkey" PRIMARY KEY, btree (id)
Has OIDs: no

test=# UPDATE test SET tsv = to_tsvector(text);
server closed the connection unexpectedly
This probably means the server terminated abnormally
before or while processing the request.
The connection to the server was lost. Attempting reset: WARNING:
terminating connection because of crash of another server process
DETAIL: The postmaster has commanded this server process to roll back
the current transaction and exit, because another server process exited
abnormally and possibly corrupted shared memory.
HINT: In a moment you should be able to reconnect to the database and
repeat your command.
Failed.
!>

Jan 15 11:32:50 brainchild postmaster[14815] general protection
rip:5bb287 rsp:7fff4ec80290 error:0

Jan 15 11:32:50 brainchild postgres[14788]: [3-1] LOG: server process
(PID 14815) was terminated by signal 11: Segmentation fault
Jan 15 11:32:50 brainchild postgres[14788]: [4-1] LOG: terminating any
other active server processes
Jan 15 11:32:50 brainchild postgres[14843]: [3-1] WARNING: terminating
connection because of crash of another server process
Jan 15 11:32:50 brainchild postgres[14843]: [3-2] DETAIL: The
postmaster has commanded this server process to roll back the current
transaction and exit, because another server
Jan 15 11:32:50 brainchild postgres[14843]: [3-3] process exited
abnormally and possibly corrupted shared memory.
Jan 15 11:32:50 brainchild postgres[14843]: [3-4] HINT: In a moment you
should be able to reconnect to the database and repeat your command.
Jan 15 11:32:50 brainchild postgres[14788]: [5-1] LOG: all server
processes terminated; reinitializing
Jan 15 11:32:50 brainchild postgres[14788]: [6-1] LOG: shmctl(1343488,
0, 0) failed: Invalid argument
Jan 15 11:32:50 brainchild postgres[14844]: [7-1] LOG: database system
was interrupted; last known up at 2008-01-15 11:32:33 CET
Jan 15 11:32:50 brainchild postgres[14844]: [8-1] LOG: database system
was not properly shut down; automatic recovery in progress
Jan 15 11:32:50 brainchild postgres[14844]: [9-1] LOG: redo starts at
8/DC07E0A0
Jan 15 11:32:54 brainchild postgres[14844]: [10-1] LOG: unexpected
pageaddr 8/BD59C000 in log file 8, segment 236, offset 5881856
Jan 15 11:32:54 brainchild postgres[14844]: [11-1] LOG: redo done at
8/EC59BEE0
Jan 15 11:32:55 brainchild postgres[14847]: [7-1] LOG: autovacuum
launcher started
Jan 15 11:32:55 brainchild postgres[14788]: [7-1] LOG: database system
is ready to accept connections

--
Best regards,
Hannes Dorbath

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Albe Laurenz 2008-01-15 11:16:42 Re: insert into ... select ... and column order
Previous Message Richard Huxton 2008-01-15 10:39:12 Re: insert into ... select ... and column order