From: | aditya desai <admad123(at)gmail(dot)com> |
---|---|
To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
Cc: | Pgsql Performance <pgsql-performance(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Query going to all paritions |
Date: | 2021-10-01 08:54:11 |
Message-ID: | CAN0SRDF3vkvOj6i8pApOWMj3EE=EgcmBdX8vXPkOQ4ZgSoynqw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
Hi Laurenz,
Please find attached explain query plan and query.
Regards,
Aditya.
On Friday, October 1, 2021, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
> On Fri, 2021-10-01 at 12:58 +0530, aditya desai wrote:
> > Hi,
> > Query on one of our partitioned tables which is range partitioned on
> "run"date" column is going to all partitions despite having run_date in
> WHERE clause. "enable_parition_pruning" is also on. I am
> > unable to generate a query plan as the query never runs fully even
> waiting for say half an hour.
> >
> > We have composite indexes on run_date,status. Do I need to create an
> index on run_date only?
>
> You need to share the query and probably the table definition. EXPLAIN
> output
> (without ANALYZE) will also help.
>
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
>
>
Attachment | Content-Type | Size |
---|---|---|
006C4247-C0E1-4329-878C-8A078B022D09.jpeg | image/jpeg | 102.6 KB |
8CDD8AB8-3B86-425D-A6FA-DB5A4A305633.jpeg | image/jpeg | 107.3 KB |
EDDE7EF8-214E-4D96-80B9-2198CBD17BFF.jpeg | image/jpeg | 117.3 KB |
431E4725-F717-4F68-B57B-9C547B3EB898.jpeg | image/jpeg | 92.9 KB |
1322075B-3D99-4FC6-810E-A067804314CB.jpeg | image/jpeg | 98.1 KB |
![]() |
image/jpeg | 58.0 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | hubert depesz lubaczewski | 2021-10-01 10:33:25 | Re: Query going to all paritions |
Previous Message | Laurenz Albe | 2021-10-01 07:53:03 | Re: Query going to all paritions |