BUG #14693: create materialized view forces btrim

From: isb0459(at)gmail(dot)com
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #14693: create materialized view forces btrim
Date: 2017-06-06 20:25:25
Message-ID: 20170606202525.1436.76268@wrigleys.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

The following bug has been logged on the website:

Bug reference: 14693
Logged by: Ian Boardman
Email address: isb0459(at)gmail(dot)com
PostgreSQL version: 9.4.9
Operating system: Fedora 23
Description:

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. In my specific case, all
the values become empty instead of yielding either the trimmed "foo" or the
"bar" fields if trimmed "foo" is empty. Is there a way to make Postgres use
the function trim as I require?

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2017-06-06 20:46:52 Re: BUG #14693: create materialized view forces btrim
Previous Message Joe Conway 2017-06-06 20:07:13 Re: BUG #14682: row level security not work with partitioned table