Re: BUG #18260: Unexpected error: "negative bitmapset member not allowed" triggered by multiple JOIN - Mailing list pgsql-bugs

From Zu-Ming Jiang
Subject Re: BUG #18260: Unexpected error: "negative bitmapset member not allowed" triggered by multiple JOIN
Date
Msg-id f257504a-07e2-408e-b007-c249c1657459@inf.ethz.ch
Whole thread Raw
In response to BUG #18260: Unexpected error: "negative bitmapset member not allowed" triggered by multiple JOIN  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
When I removed "window w0 as (partition by ref_33.c_3 order by 
ref_33.c_4 desc)" in the test case query, the query did not trigger 
errors any more.

Specifically, this query did not trigger errors:

with cte_1 as (select
     ref_1.c_0 as c_2,
     ref_1.c_4 as c_3,
     case when (nullif(ref_1.c_2, ref_1.c_0) <> (
           select
               ref_53.c_2 as c_0
             from
               (t1 as ref_52 left outer join t3 as ref_53 on true)
             where (ref_53.c_6) ~~ (ref_53.c_6)
             order by c_0 limit 1)
           ) then null else null end
          as c_4
   from
     t3 as ref_1)
select 1
   from
     cte_1 as ref_33
   where (ref_33.c_2 > (
         select
             ref_200.c_2 as c_0
           from
             t3 as ref_200
           order by c_0 limit 1));



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #18260: Unexpected error: "negative bitmapset member not allowed" triggered by multiple JOIN
Next
From: PG Bug reporting form
Date:
Subject: BUG #18261: Inconsistent results of SELECT affected by joined subqueries