lsasoft.com>>
> > Sent: 14 February 2019 16:10:01
> > To: suganthi Sekar
> > Cc: pgsql-performance@lists.postgresql.org > pgsql-performance@lists.postgresql.org>
> > Subject: Re: constraint exclusion with ineq condition (Re: server hardware
> > tuning.)
> &
--
> *From:* Michael Lewis
> *Sent:* 15 February 2019 00:20:00
> *To:* suganthi Sekar
> *Cc:* Justin Pryzby; pgsql-performance@lists.postgresql.org
> *Subject:* Re: constraint exclusion with ineq condition (Re: server
> hardware tuning.)
>
> Yeah, the planner doesn
are there.
Regards,
Suganthi Sekar
From: Michael Lewis
Sent: 15 February 2019 00:20:00
To: suganthi Sekar
Cc: Justin Pryzby; pgsql-performance@lists.postgresql.org
Subject: Re: constraint exclusion with ineq condition (Re: server hardware
tuning.)
Yeah, the
e column call_created_date
>
> From: Michael Lewis
> Sent: 14 February 2019 19:35:48
> To: suganthi Sekar
> Cc: Justin Pryzby; pgsql-performance@lists.postgresql.org
> Subject: Re: constraint exclusion with ineq condition (Re: server hardware
> tuning.)
Both table Portion by same column call_created_date
From: Michael Lewis
Sent: 14 February 2019 19:35:48
To: suganthi Sekar
Cc: Justin Pryzby; pgsql-performance@lists.postgresql.org
Subject: Re: constraint exclusion with ineq condition (Re: server hardware
tuning
hi 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 +, suganthi Sekar wrote:
> > u mean the below parameter need to set on . its already on only.
>
gards
Suganthi Sekar
From: Justin Pryzby
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 +, suganthi S
erformance@lists.postgresql.org
Subject: Re: constraint exclusion with ineq condition (Re: server hardware
tuning.)
On Thu, Feb 14, 2019 at 09:38:52AM +, suganthi Sekar wrote:
> i am using Postgresql 11, i have 2 partition table , when i joined both
> table in query
> a table its goes exact partition
On Thu, Feb 14, 2019 at 10:38:36AM +, 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_c
On Thu, Feb 14, 2019 at 09:38:52AM +, suganthi Sekar wrote:
> i am using Postgresql 11, i have 2 partition table , when i joined both
> table in query
> a table its goes exact partition table , but other table scan all partition
>
> please clarify on this .
>
> Example :
>
> explain anal
10 matches
Mail list logo
