Re: BUG #16368: Incorrect function inlining in the presence of a window function

From: Elvis Pranskevichus <elprans(at)gmail(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #16368: Incorrect function inlining in the presence of a window function
Date: 2020-04-16 02:06:39
Message-ID: 2352640.BRP1sDCPNr@hammer.magicstack.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> The particular case mentioned there seems to be about the same as
> here: constant-folding happens even in CASE arms that will never be
> reached at runtime.

Since the actual issue here is false positive exceptions, why can't we
treat errors raised during const eval as a signal to cancel the constant
folding, i.e. ignore them and keep the failing expression unoptimized?

Elvis

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2020-04-16 05:30:36 Re: BUG #16369: Segmentation Faults and Data Corruption with Generated Columns
Previous Message Elvis Pranskevichus 2020-04-16 01:17:30 Re: BUG #16368: Incorrect function inlining in the presence of a window function