From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | damir(dot)ciganovic(dot)jankovic(at)gmail(dot)com |
Cc: | pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #15933: Partition by multiple columns bug |
Date: | 2019-07-30 14:34:21 |
Message-ID: | 12154.1564497261@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
PG Bug reporting form <noreply(at)postgresql(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Langote | 2019-07-31 04:58:27 | Re: BUG #15933: Partition by multiple columns bug |
Previous Message | PG Bug reporting form | 2019-07-30 07:53:20 | BUG #15933: Partition by multiple columns bug |