Re: BUG #16712: Wrong Sub-Query Record Filtering - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: BUG #16712: Wrong Sub-Query Record Filtering
Date
Msg-id CAKFQuwZXqzhmf5vp1w7eu0MnCP6=y=b5sb8e6nmkgVViF2Rpdg@mail.gmail.com
Whole thread Raw
In response to BUG #16712: Wrong Sub-Query Record Filtering  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
On Thu, Nov 12, 2020 at 7:34 AM PG Bug reporting form <noreply@postgresql.org> wrote:
The following bug has been logged on the website:

Bug reference:      16712
Logged by:          SP
Email address:      bugatti2.5sp@gmail.com
PostgreSQL version: 13.0
Operating system:   seems any (tested on Ubuntu 18.04 and macOS 10.15)
Description:       

An unexpected result returns when running this query:

WITH data_cte(str) AS (
    SELECT *
    FROM (VALUES ('a')) data_tmp(str)
    WHERE FALSE
)
SELECT str::INTEGER
FROM data_cte;

While empty result is expected, we get this:

ERROR:  invalid input syntax for type integer: "a"

Because of these type casting error, it seems that the outer query has
access to the data_cte record!


It does - right there in the "FROM data_cte" clause.  The planner has chosen to optimize this query by taking the two parts and making them one, reducing a level of execution indirection.  If you don't wish for this to happen you need to add MATERIALIZED to the WITH clause element.  This is one of the more impactful changes with v13, in prior versions materialized was the default (and optimization was not possible).

David J.

pgsql-bugs by date:

Previous
From: PG Bug reporting form
Date:
Subject: BUG #16712: Wrong Sub-Query Record Filtering
Next
From: Tom Lane
Date:
Subject: Re: Problem with extract function ?