Hi,
yes i accept , but when i will do for existing tables, i am facing issue.
I have created 100 Function , all the function having five table join(now all partition by date) , now its not possible to change where condition in all 100 Function.
so that i am trying any other possibilities are there.
Regards,
Suganthi Sekar
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Sent: 15 February 2019 00:20:00
To: suganthi Sekar
Cc: Justin Pryzby; pgsql-performance@xxxxxxxxxxxxxxxxxxxx
Subject: Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
Yeah, the planner doesn't know that call_created_date can be limited on both tables unless you tell it specify it in the where condition as Laurenz said on another thread.
Both table Portion by same column call_created_date
________________________________
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Sent: 14 February 2019 19:35:48
To: suganthi Sekar
Cc: Justin Pryzby;
pgsql-performance@xxxxxxxxxxxxxxxxxxxx
Subject: Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
What are these two tables partitioned by?
On Thu, Feb 14, 2019, 5:03 AM suganthi Sekar <suganthi@xxxxxxxxxxxx<mailto:suganthi@xxxxxxxxxxxx> wrote:
Hi,
Thanks, i know if explicitly we give in where condition it is working.
i thought with below parameter in Postgresq11 this issue is fixed ?
enable_partitionwise_join to 'on';
what is the use of enable_partitionwise_join to 'on';
Thanks for your response.
Regards
Suganthi Sekar
________________________________
From: Justin Pryzby <pryzby@xxxxxxxxxxxxx<mailto:pryzby@xxxxxxxxxxxxx>>
Sent: 14 February 2019 16:10:01
To: suganthi Sekar
Cc: pgsql-performance@xxxxxxxxxxxxxxxxxxxx<mailto:pgsql-performance@xxxxxxxxxxxxxxxxxxxx>
Subject: Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
On Thu, Feb 14, 2019 at 10:38:36AM +0000, suganthi Sekar wrote:
> u mean the below parameter need to set on . its already on only.
> alter system set constraint_exclusion to 'on';
No, I said:
> You can work around it by specifying the same condition on b.call_created_date:
> > AND b.call_created_date >='2017-11-01' AND b.call_created_date<'2017-11-30'
|
