Re: literal vs dynamic partition constraint in plan execution - Mailing list pgsql-general

From Michael Lewis
Subject Re: literal vs dynamic partition constraint in plan execution
Date
Msg-id CAHOFxGoG-urMdPxHD2OTUvAWBTsMsdO5f7ywyefLC5GNxgsofQ@mail.gmail.com
Whole thread Raw
In response to Re: literal vs dynamic partition constraint in plan execution  (Luca Ferrari <fluca1978@gmail.com>)
List pgsql-general
I think I would expect this behavior with how you have defined the constraints as the function results rather than just being strict comparisons to the timestamp field.

Instead of this-
Check constraints:
>     "y2018_mis_ora_check" CHECK (date_part('year'::text, mis_ora) =
> 2018::double precision)

I would expect this-
Check constraints:
>     "y2018_mis_ora_check" CHECK mis_ora) >= make_timestamp(2018, 1,
> 1, 0, 0, 0::double precision) AND < make_timestamp(2019, 1,
> 1, 0, 0, 0::double precision)

pgsql-general by date:

Previous
From: Michael Lewis
Date:
Subject: Re: Bad Estimate for multi tenant database queries
Next
From: Adrian Klaver
Date:
Subject: Re: Upgrade 96 -> 11