Re: BUG #15933: Partition by multiple columns bug

On Tue, Jul 30, 2019 at 11:34 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> 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.

Yeah, I think we fixed this particular issue in 6630ccad7a [1] that
appeared in the 11.4 release.

Thanks,
Amit

[1] https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=6630ccad7a