Re: making tsearch2 dictionaries - Mailing list pgsql-general

From Tom Lane
Subject Re: making tsearch2 dictionaries
Date
Msg-id 25708.1076945172@sss.pgh.pa.us
Whole thread Raw
In response to Re: making tsearch2 dictionaries  (Ben <bench@silentmedia.com>)
Responses Re: making tsearch2 dictionaries  (Teodor Sigaev <teodor@sigaev.ru>)
List pgsql-general
Ben <bench@silentmedia.com> writes:
> Okay, so I was actually able to answer this question on my own, in a
> manner of speaking. It seems the way to do this is to merely return a
> larger char** array, with one element for each word. But I was having
> trouble with postgres crashing, because (I think) it tries to free each
> element independently before using all of them. I had set each element
> to a different null-terminated chunk of the same palloc'd memory
> segment. Having never written C stored procs before, I take it that's
> bad practice?

Given Teodor's response, I think the issue is probably that you were
palloc'ing in too short-lived a context.  But whatever the problem is,
you'll narrow it down a lot faster if you build with --enable-cassert.
I wouldn't ever recommend trying to debug C functions without that.

            regards, tom lane

pgsql-general by date:

Previous
From: Terry Lee Tucker
Date:
Subject: Re: Dazed and Confused
Next
From: Mikhail Terekhov
Date:
Subject: Re: Using NOTIFY... Slow Client Querys