Re: record identical operator - Mailing list pgsql-hackers

From Dimitri Fontaine
Subject Re: record identical operator
Date
Msg-id m2y56t42f4.fsf@2ndQuadrant.fr
Whole thread Raw
In response to Re: record identical operator  (Kevin Grittner <kgrittn@ymail.com>)
Responses Re: record identical operator  (Hannu Krosing <hannu@2ndQuadrant.com>)
Re: record identical operator  (Kevin Grittner <kgrittn@ymail.com>)
Re: record identical operator  (Alvaro Herrera <alvherre@2ndquadrant.com>)
List pgsql-hackers
Kevin Grittner <kgrittn@ymail.com> writes:
> There are examples in the patch and this thread, but rather than
> reference back to those I'll add a new one.  Without the patch:

Thanks much for doing that.

> 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, so that the two relations actually yield the same
results for the right definition of "same" here: the citext one.

In other words, the results only look different in ways that don't
matter for the datatype involved, and I think that if it matters to the
user then he needs to review is datatype choices or view definition.

So my position on that is that your patch is only adding confusion for
no benefits that I'm able to understand.

Regards,
--
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: logical changeset generation v6
Next
From: Andres Freund
Date:
Subject: Re: [RFC] Extend namespace of valid guc names