Re: constraint exclusion with ineq condition (Re: server hardware tuning.)
От | Michael Lewis |
---|---|
Тема | Re: constraint exclusion with ineq condition (Re: server hardware tuning.) |
Дата | |
Msg-id | CAHOFxGqdAaA_Ryzx22hG-U-dj0c6d55hGj=ythCkYZNLGCpSOQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: constraint exclusion with ineq condition (Re: server hardwaretuning.) (suganthi Sekar <suganthi@uniphore.com>) |
Ответы |
Re: constraint exclusion with ineq condition (Re: server hardwaretuning.)
|
Список | pgsql-performance |
What are these two tables partitioned by?
On Thu, Feb 14, 2019, 5:03 AM suganthi Sekar <suganthi@uniphore.com 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.RegardsSuganthi SekarFrom: 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.)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'
В списке pgsql-performance по дате отправления: