From: | Marc Millas <marc(dot)millas(at)mokadb(dot)com> |
---|---|
To: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: need explanation about an explain plan |
Date: | 2023-06-28 15:29:27 |
Message-ID: | CADX_1aYVmbrbJi+62b06XWuLzn6CJs6P0K=wEDinJjcGvkuC+g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Sorry, gmail sent uncompleted message
Hi,
Postgres 14.2 (for one more month)
The explain plan and request is here:
https://explain.depesz.com/s/Opk0
The big table (10 billions raws) is split in around 130 partitions, one by
month.
the ladate column is the partition key, and it does have 1 value for each
partition.
there is an index on the numfic column. the distribution of values for that
column may differ before and after 2019 january.
The request is executed in a loop for all ten years of data, year 1,2,3,
then year2,3,4 etc
that request is also executed for columns other than cod, one column at a
time (there are 107 columns...)
I dont understand why the planner use a filter on the date, as its already
within the partition structure.
Thanks,
Marc MILLAS
On Wed, Jun 28, 2023 at 5:22 PM Marc Millas <marc(dot)millas(at)mokadb(dot)com> wrote:
> Hi,
>
> Postgres 14.2 (for one more month)
> The explain plan and request is here:
> https://explain.depesz.com/s/Opk0
>
> The big table is split in around 130 partitions, one by month.
> the ladate column is the partition key, and it does have 1 value for each
> partition.
> there is a
>
>
>
>
> Marc MILLAS
> Senior Architect
> +33607850334
> www.mokadb.com
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Laurenz Albe | 2023-06-28 16:48:20 | Re: need explanation about an explain plan |
Previous Message | Marc Millas | 2023-06-28 15:22:12 | need explanation about an explain plan |