Re: [BUGS] BUG #14693: create materialized view forces btrim - Mailing list pgsql-bugs

From David G. Johnston
Subject Re: [BUGS] BUG #14693: create materialized view forces btrim
Date
Msg-id CAKFQuwZa82r7L+z6QfW9O+jg9H_iuwhTgWLoo9HRK5KLvrJ1Jw@mail.gmail.com
Whole thread Raw
In response to [BUGS] BUG #14693: create materialized view forces btrim  (isb0459@gmail.com)
List pgsql-bugs
On Tue, Jun 6, 2017 at 1:25 PM, <isb0459@gmail.com> wrote:
I am trying to create a materialized view. I have a working SQL query that
uses this expression: coalesce(trim(foo), bar). When I use that in the
definition for create materialized view, Postgres force replaces the trim()
call into a btrim() and breaks the query result.

Given your subsequent descriptions I'm confused as to your claim that you have a working SQL query when not used as part of a create materialized view.​  You should have found that running the same simple select by itself was always returning empty foo strings instead of bar.

David J.

pgsql-bugs by date:

Previous
From: Mike Palmiotto
Date:
Subject: Re: [BUGS] BUG #14682: row level security not work with partitioned table
Next
From: Heikki Linnakangas
Date:
Subject: Re: [BUGS] [PATCH] Fixed malformed error message on malformed SCRAMmessage.