On 2013-09-19 05:33:22 -0700, Kevin Grittner wrote:
> Dimitri Fontaine <dimitri@2ndQuadrant.fr> wrote:
> > Kevin Grittner <kgrittn@ymail.com> writes:
>
> >> The problem, as I see it, is that the view and the concurrently
> >> refreshed materialized view don't yield the same results for the
> >> same query. The rows are equal, but they are not the same.
> >> With the patch the matview, after RMVC, looks just the same as
> >> the view.
> >
> > My understanding is that if you choose citext then you don't care
> > at all about the case
>
> That's not my understanding. If that was what citext was for it
> would be much simpler to force the case in creating each value. It
> *preserves* the case for display, but ignores it for comparisons.
> That's the contract of the type, like it or not. "Equal" does not
> mean "the same". They clearly want to preserve and display
> differences among equal values.
I agree.
I am not 100% sure if the can of worms this opens is worth the trouble,
but from my POV it's definitely an understandable and sensible goal.
My complaints about this "subfeature" were never about trying to get
that right for matviews...
Greetings,
Andres Freund
-- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services