Message-ID: <9b0fc158ae0701e0e3cbd03d7f022735dc4e3f24.camel@cybertec.at>
Subject: Re: Query going to all paritions
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: aditya desai <admad123@gmail.com>, Pgsql Performance
	 <pgsql-performance@lists.postgresql.org>
Date: Fri, 01 Oct 2021 09:53:03 +0200
In-Reply-To: 
 <CAN0SRDFTummB0w5L_ijZq+ufZx8s6+Wdm96SEwqkQZYeUjpf=w@mail.gmail.com>
References: 
	<CAN0SRDFTummB0w5L_ijZq+ufZx8s6+Wdm96SEwqkQZYeUjpf=w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.40.4 (3.40.4-1.fc34) 
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Archived-At: 
 <https://www.postgresql.org/message-id/9b0fc158ae0701e0e3cbd03d7f022735dc4e3f24.camel%40cybertec.at>
Precedence: bulk

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