Re: tuplesort: unexpected end of data

Hi!
I should say that this error is a non-deterministic one. It happened 
once/twenty...

-------------------------------explain info---------------------------------
spid=> explain insert into warehouse_tmp (uri, expression, n, relevance, spid_measure, size, title, sample)
spid->    select d.uri, dn.expression, n.n, dn.relevance, d.spid_measure, d.size, d.title, dn.sample
spid->    from document as d
spid->         inner join (document_n_gram as dn
spid(>                     inner join n_gram as n
spid(>                     on (dn.expression = n.expression))
spid->         on (d.uri = dn.uri)
spid->    order by dn.expression asc, n.n asc ;
NOTICE:  QUERY PLAN:

Subquery Scan *SELECT*  (cost=3895109.07..3895109.07 rows=1009271 width=886) ->  Sort  (cost=3895109.07..3895109.07
rows=1009271width=886)       ->  Hash Join  (cost=1155071.81..2115045.12 rows=1009271 width=886)             ->  Merge
Join (cost=1154294.92..1170599.85 rows=1009271 width=588)                   ->  Sort  (cost=1001390.67..1001390.67
rows=1009271width=439)                         ->  Seq Scan on document_n_gram dn  (cost=0.00..49251.71 rows=1009271
width=439)                  ->  Sort  (cost=152904.25..152904.25 rows=466345 width=149)                         ->  Seq
Scanon n_gram n  (cost=0.00..12795.45 rows=466345 width=149)             ->  Hash  (cost=767.71..767.71 rows=3671
width=298)                  ->  Seq Scan on document d  (cost=0.00..767.71 rows=3671 width=298)
 

EXPLAIN
spid=> 
----------------------------------------------------------------------------
If you need more info, just ask. I'll be glad to contribute to a so 
interesting project! :-)

--     o__        Bem haja,   _.>/ _            NunoACHenriques  (_) \(_)            ~~~~~~~~~~~~~~~
http://students.fct.unl.pt/users/nuno/

On Sun, 9 Jun 2002, Tom Lane wrote:

>NunoACHenriques <nach@fct.unl.pt> writes:
>> Jun  2 06:29:37 srv31 postgres[2986]: [57279] ERROR:  tuplesort: unexpected end of data
>
>Hmm.  This is an internal consistency check in the sort code.  Perhaps
>you've found a bug, but there's not enough info here to do much.  Can
>you provide the EXPLAIN plan for the query that's triggering the error?
>
>            regards, tom lane
>