Re: BUG #15933: Partition by multiple columns bug
От | Tom Lane |
---|---|
Тема | Re: BUG #15933: Partition by multiple columns bug |
Дата | |
Msg-id | 12154.1564497261@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | BUG #15933: Partition by multiple columns bug (PG Bug reporting form <noreply@postgresql.org>) |
Ответы |
Re: BUG #15933: Partition by multiple columns bug
|
Список | 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 по дате отправления: