| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | Ian Boardman <isb0459(at)gmail(dot)com> |
| Cc: | "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14693: create materialized view forces btrim |
| Date: | 2017-06-07 14:36:45 |
| Message-ID: | CAKFQuwZa82r7L+z6QfW9O+jg9H_iuwhTgWLoo9HRK5KLvrJ1Jw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Jun 6, 2017 at 1:25 PM, <isb0459(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2017-06-07 14:48:23 | Re: [PATCH] Fixed malformed error message on malformed SCRAM message. |
| Previous Message | Mike Palmiotto | 2017-06-07 13:49:27 | Re: BUG #14682: row level security not work with partitioned table |