> > I have encountered strange errors while testing PostgreSQL 8.4 beta2.
>
> > ERROR: tuple offset out of range: 0
> > (occasionally ERROR: tuple offset out of range: 459)
>
> This is evidently coming from tbm_add_tuples, indicating that it's being
> passed bogus TID values from the GIN index. We'll probably have to get
> Teodor to look at it --- can you provide a self-contained test case?
Sorry for delay. I have put a database dump at:
http://sylpheed.sraoss.jp/tmp/dump.sql.gz
We got following errors using this database:
ERROR: unrecognized operator: -50
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
NOTICE: text-search query contains only stop words or doesn't contain lexemes, ignored
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: 0
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'interval') @@ body_index
ERROR: tuple offset out of range: 924
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'pitr') @@ body_index
--
Tatsuo Ishii
SRA OSS, Inc. Japan