Re: partition pruning - Mailing list pgsql-performance

From Justin Pryzby
Subject Re: partition pruning
Date
Msg-id 20190214143611.GG30291@telsasoft.com
Whole thread Raw
In response to Re: partition pruning  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-performance
On Thu, Feb 14, 2019 at 01:37:49PM +0100, Laurenz Albe wrote:
> There is no condition on the table "call_report2" in your query,
> so it is not surprising that all partitions are scanned, right?

Some people find it surprising, since: a.call_id=b.call_id

suganthi Sekar wrote:
> > explain analyze
> > select * from call_report1 as a  inner join  call_report2 as b on a.call_id=b.call_id
> >  where a.call_created_date ='2017-11-01' and '2017-11-30'

Justin


pgsql-performance by date:

Previous
From: suganthi Sekar
Date:
Subject: Re: constraint exclusion with ineq condition (Re: server hardwaretuning.)
Next
From: Mariel Cherkassky
Date:
Subject: Re: autovacuum big table taking hours and sometimes seconds