Thread: contrib/tsearch in postgresql 7.2 (fwd)

contrib/tsearch in postgresql 7.2 (fwd)

From
Oleg Bartunov
Date:
Hi,

we've got a message from Poul about problem with our contrib modules
tsearch and I dont' know yet if this could be really tsearch problem,
it's time to go to the bed :-) Could be this problem related to the
partial index he used ?
Regards,    Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83

---------- Forwarded message ----------
Date: Mon, 04 Feb 2002 23:37:49 +0100
From: Poul L. Christiansen <poulc@cs.auc.dk>
To: teodor@stack.net, oleg@sai.msu.su
Subject: contrib/tsearch in postgresql 7.2

Hi

I'm testing your tsearch module for postgresql 7.2 (just downloaded the
final release a few hours ago) and I get this error:

ERROR:  MemoryContextAlloc: invalid request size 0

when I create an index on an txtidx column.

SQL:
create index article_articletextftinon12k88 on article using
gist(indexarticletext) where paperid=1000 and
char_length(rawarticletext) <12880;

And I have located the reason for this error: If the field I populated
the txtidx column from is greater than 12850 it get the error. When the
size is less than 12850, it works fine.

I'm using PostgreSQL on Mandrake 8.1, with Linux kernel 2.4.17

The error also appears on PostgreSQL 7.2beta4 on Linux 2.2

Is there really a 12850 byte size limitation ? If there is, it should be
documented ;)

Poul L. Christiansen



Re: contrib/tsearch in postgresql 7.2 (fwd)

From
Tom Lane
Date:
Oleg Bartunov <oleg@sai.msu.su> writes:
> we've got a message from Poul about problem with our contrib modules
> tsearch and I dont' know yet if this could be really tsearch problem,
> it's time to go to the bed :-) Could be this problem related to the
> partial index he used ?

Seems unlikely.  But in any case, you'd be more likely to get help
by giving a complete script for reproducing the problem.  I'm not
feeling like reverse-engineering Poul's table schema and then guessing
at his data too...
        regards, tom lane


Re: contrib/tsearch in postgresql 7.2 (fwd)

From
Oleg Bartunov
Date:
On Mon, 4 Feb 2002, Tom Lane wrote:

> Oleg Bartunov <oleg@sai.msu.su> writes:
> > we've got a message from Poul about problem with our contrib modules
> > tsearch and I dont' know yet if this could be really tsearch problem,
> > it's time to go to the bed :-) Could be this problem related to the
> > partial index he used ?
>
> Seems unlikely.  But in any case, you'd be more likely to get help
> by giving a complete script for reproducing the problem.  I'm not
> feeling like reverse-engineering Poul's table schema and then guessing
> at his data too...
>
>             regards, tom lane

yes, the problem is persistent without a partial index, he said.
I already ask him about test suite.

>
Regards,    Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83



Re: contrib/tsearch in postgresql 7.2 (fwd)

From
Oleg Bartunov
Date:
We found the problem and will submit a patch for 7.2.1.
We were confused by 'index toasting' and thought index is realy toasted
but actually it's only compressed. So, we have to rollback our
changes for intarray and tsearch :-(  We were happy to make gist index
non-lossy, but it's not the case for long data. Probably it'd be
possible to define in compile time if index will be lossy.

Tom, does index compressing is a temporal solution ? Do you intend
to implement real toasting ?
Oleg

On Mon, 4 Feb 2002, Tom Lane wrote:

> Oleg Bartunov <oleg@sai.msu.su> writes:
> > we've got a message from Poul about problem with our contrib modules
> > tsearch and I dont' know yet if this could be really tsearch problem,
> > it's time to go to the bed :-) Could be this problem related to the
> > partial index he used ?
>
> Seems unlikely.  But in any case, you'd be more likely to get help
> by giving a complete script for reproducing the problem.  I'm not
> feeling like reverse-engineering Poul's table schema and then guessing
> at his data too...
>
>             regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
Regards,    Oleg
_____________________________________________________________
Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
Sternberg Astronomical Institute, Moscow University (Russia)
Internet: oleg@sai.msu.su, http://www.sai.msu.su/~megera/
phone: +007(095)939-16-83, +007(095)939-23-83