Re: constraint exclusion with ineq condition (Re: server hardwaretuning.)
| От | suganthi Sekar |
|---|---|
| Тема | Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) |
| Дата | |
| Msg-id | SG2PR01MB29677E0B9863A71DBD86DF0FBC670@SG2PR01MB2967.apcprd01.prod.exchangelabs.com обсуждение исходный текст |
| Ответ на | Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) (Justin Pryzby <pryzby@telsasoft.com>) |
| Ответы |
Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
|
| Список | 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@telsasoft.com>
Sent: 14 February 2019 16:10:01
To: suganthi Sekar
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
Sent: 14 February 2019 16:10:01
To: suganthi Sekar
Cc: pgsql-performance@lists.postgresql.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'
> 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'
В списке pgsql-performance по дате отправления: