Re: Evaluate expression at planning time for two more cases

From: Surafel Temesgen <surafel3000(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Ashutosh Bapat <ashutosh(dot)bapat(at)2ndquadrant(dot)com>
Subject: Re: Evaluate expression at planning time for two more cases
Date: 2020-11-24 07:47:25
Message-ID: CALAY4q98fWkfYROZ2iy7CNuBi4JGKRhAUg6-jVxkGY2vzaJinA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Pavel Borisov,
It's always good to select the optimal way even if it didn't have
performance gain
but in case of this patch i see 4x speed up on my laptop and it will work
on any
table that have NULL constraint

regards
Surafel

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message ROS Didier 2020-11-24 08:09:29 Migration Oracle multitenant database to PostgreSQL ?
Previous Message Tatsuro Yamada 2020-11-24 07:46:28 Huge memory consumption on partitioned table with FKs