Re: constraint exclusion with ineq condition (Re: server hardware tuning.)

From: suganthi Sekar <suganthi(at)uniphore(dot)com>
To: Justin Pryzby <pryzby(at)telsasoft(dot)com>
Cc: "pgsql-performance(at)lists(dot)postgresql(dot)org" <pgsql-performance(at)lists(dot)postgresql(dot)org>
Subject: Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
Date: 2019-02-14 10:49:16
Message-ID: SG2PR01MB29677E0B9863A71DBD86DF0FBC670@SG2PR01MB2967.apcprd01.prod.exchangelabs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

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(at)telsasoft(dot)com>
Sent: 14 February 2019 16:10:01
To: suganthi Sekar
Cc: pgsql-performance(at)lists(dot)postgresql(dot)org
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'

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Laurenz Albe 2019-02-14 12:37:49 Re: partition pruning
Previous Message Justin Pryzby 2019-02-14 10:40:01 Re: constraint exclusion with ineq condition (Re: server hardware tuning.)