Re: BUG #15933: Partition by multiple columns bug - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #15933: Partition by multiple columns bug
Date
Msg-id 12154.1564497261@sss.pgh.pa.us
Whole thread Raw
In response to BUG #15933: Partition by multiple columns bug  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #15933: Partition by multiple columns bug  (Amit Langote <amitlangote09@gmail.com>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> -- fourth query that completely fails to find partition
> EXPLAIN ANALYZE SELECT * from my_table WHERE my_enum = 'FIRST' AND my_time >
> now();
> Result  (cost=0.00..0.00 rows=0 width=16) (actual time=0.001..0.001 rows=0
> loops=1)
>    One-Time Filter: false
> This seems like a bug to me.

In v11 branch tip I get

 Append  (cost=0.00..42.39 rows=3 width=16) (actual time=0.007..0.007 rows=0 loops=1)
   ->  Seq Scan on my_table_first  (cost=0.00..42.38 rows=3 width=16) (actual time=0.006..0.006 rows=0 loops=1)
         Filter: ((my_enum = 'FIRST'::enum1) AND (my_time > now()))

and in HEAD it looks like

 Seq Scan on my_table_first  (cost=0.00..42.38 rows=3 width=16) (actual time=0.007..0.007 rows=0 loops=1)
   Filter: ((my_enum = 'FIRST'::enum1) AND (my_time > now()))

so evidently this is already fixed.

            regards, tom lane



pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #15933: Partition by multiple columns bug
Next
From: Amit Langote
Date:
Subject: Re: BUG #15933: Partition by multiple columns bug