> > I found the cause of this one --- the new code for estimating the
> > selectivity of @@ was not guarding against the possibility that the
> > given TSQuery is empty, as it is in this example.
>
> Shouldn't be this in regression test?
>
> > I'm still unable to reproduce the "tuple offset out of range" errors.
>
> Maybe this is due to the difference how the index is physically
> organized. I will uplaod physical database cluster.
Done.
http://sylpheed.sraoss.jp/tmp/searcherdb84.tar.bz2
$ psql -U hiro sylph
Pager usage is off.
psql (8.4beta2)
Type "help" for help.
sylph=# SELECT msg_sid, hdr_from, hdr_to, hdr_subject, msg_date, folder_id, msgnum FROM msginfo LEFT JOIN
msg_folderinfoUSING (msg_sid) WHERE plainto_tsquery(E'a') @@ body_index;
NOTICE: text-search query contains only stop words or doesn't contain lexemes, ignored
ERROR: unrecognized operator: 24
STATEMENT: SELECT msg_sid, hdr_from, hdr_to, hdr_subject, msg_date, folder_id, msgnum FROM msginfo LEFT JOIN
msg_folderinfoUSING (msg_sid) WHERE plainto_tsquery(E'a') @@ body_index;
ERROR: unrecognized operator: 24
sylph=# SELECT msg_sid, hdr_from, hdr_to, hdr_subject, msg_date, folder_id, msgnum FROM msginfo LEFT JOIN
msg_folderinfoUSING (msg_sid) WHERE plainto_tsquery(E'tsearch') @@ body_index;
ERROR: tuple offset out of range: 609
STATEMENT: SELECT msg_sid, hdr_from, hdr_to, hdr_subject, msg_date, folder_id, msgnum FROM msginfo LEFT JOIN
msg_folderinfoUSING (msg_sid) WHERE plainto_tsquery(E'tsearch') @@ body_index;
ERROR: tuple offset out of range: 609
--
Tatsuo Ishii
SRA OSS, Inc. Japan