Re: Backend crash with tsearch

From: Teodor Sigaev <teodor(at)stack(dot)net>
To: "Magnus Naeslund(f)" <mag(at)fbab(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Backend crash with tsearch
Date: 2002-12-03 16:10:10
Message-ID: 3DECD762.7040908@stack.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Does it crashed?
# select txt2txtidx('Can - Live 1971-77');

Line txtidx.c:366 :
lemm = lemmatize(token, &lenlemm, type);

lemmatize() is defined in morph.c. Did you use another modules for postgresql?

It seems to me that we see a name conflict. Function lemmatize is defined in
somewhere also.

Magnus Naeslund(f) wrote:
> More info, the gdb> sharedlibrary loaded some more symbols:
>
> (gdb) bt
> #0 0x02d10000 in ?? ()
> #1 0x401faf48 in parsetext (prs=0xbfffea60, buf=0x4277eb3c "Can - Live
> 1971-77", buflen=18) at txtidx.c:366
> #2 0x401fb5e6 in txt2txtidx (fcinfo=0xbfffeaf0) at txtidx.c:487
> #3 0x080ec45c in ExecMakeFunctionResult (fcache=0x83172bc,
> arguments=0x831187c, econtext=0x8317114, isNull=0xbfffec8f "",
> isDone=0xbfffecd8) at execQual.c:839
> #4 0x080ed023 in ExecEvalExpr (expression=0x8311898,
> econtext=0x8317114, isNull=0xbfffec8f "", isDone=0xbfffecd8)
> at execQual.c:1168
> #5 0x080ed3c4 in ExecTargetList (targetlist=0x8311b20, nodomains=21,
> targettype=0x8312b1c, values=0x83180a0,
> econtext=0x8317114, isDone=0xbfffee78) at execQual.c:2058
> #6 0x080ed7bf in ExecProject (projInfo=0x8317f90, isDone=0xbfffee78) at
> execQual.c:2282
> #7 0x080ed8a9 in ExecScan (node=0x8315e60, accessMtd=0x80f4fa0
> <SeqNext>) at execScan.c:133
> #8 0x080f4e73 in ExecSeqScan (node=0x8315e60) at nodeSeqscan.c:133
> #9 0x080eafbc in ExecProcNode (node=0x8315e60, parent=0x0) at
> execProcnode.c:291
> #10 0x080e99f7 in ExecutePlan (estate=0x83161ac, plan=0x8315e60,
> operation=CMD_UPDATE, numberTuples=0,
> direction=ForwardScanDirection, destfunc=0x8317fbc) at
> execMain.c:954
> #11 0x080ea999 in ExecutorRun (queryDesc=0x831718c, estate=0x83161ac,
> direction=ForwardScanDirection, count=0) at execMain.c:195
> #12 0x08143b9b in ProcessQuery (parsetree=0x830c8c4, plan=0x8315e60,
> dest=Remote, completionTag=0xbffff060 "") at pquery.c:242
> #13 0x08141dc1 in pg_exec_query_string (query_string=0x830c79c,
> dest=Remote, parse_context=0x82d6e88) at postgres.c:838
> #14 0x08142e1d in PostgresMain (argc=4, argv=0xbffff2e0,
> username=0x82c23a9 "mag") at postgres.c:2016
> #15 0x08125544 in DoBackend (port=0x82c2278) at postmaster.c:2293
> #16 0x08124e5c in BackendStartup (port=0x82c2278) at postmaster.c:1915
> #17 0x0812430d in ServerLoop () at postmaster.c:1000
> #18 0x08123e94 in PostmasterMain (argc=1, argv=0x8276d00) at
> postmaster.c:779
> #19 0x080fefe2 in main (argc=1, argv=0xbffffc74) at main.c:210
> #20 0x42017589 in __libc_start_main () from /lib/i686/libc.so.6
>
>
> Magnus
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org
>

--
Teodor Sigaev
teodor(at)stack(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Naeslund(f) 2002-12-03 16:12:31 Re: Backend crash with tsearch
Previous Message Bruce Momjian 2002-12-03 16:08:50 Re: 7.3 -> pg_atoi: zero-length string