Re: Different results from identical matviews

From: Anders Steinlein <anders(at)e5r(dot)no>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Different results from identical matviews
Date: 2020-07-02 22:05:27
Message-ID: CAC35HNnZe9rx9X5TZxWJgdhk_5H_KHTMCT9jnZP2RDO84i7n4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Jul 2, 2020 at 11:44 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> Anders Steinlein <anders(at)e5r(dot)no> writes:
> > I'm reading this correctly, would this be a "reason" to be more explicit
> > when doing joins involving non-standard data types? I.e. would it be
> > "safer" to do ON x1.email::citext == x2.email::citext instead of USING
> (if
> > there is any difference at all...)?
>
> Yes, it would be. Of course then you don't get the "merging" of the two
> join output columns into one, so you might have to qualify references a
> bit more.
>
> You might find this thread interesting:
>
>
> https://www.postgresql.org/message-id/flat/ffefc172-a487-aa87-a0e7-472bf29735c8%40gmail.com

Indeed interesting, thanks!

Am I right in thinking that we should actually go over (i.e. re-create) all
functions and views defined before this dump/restore where we're using JOIN
... USING (citext_column)? We most definitely have many more such cases,
since this is the common (perhaps naive) way we've written joins (unless
there are obvious reasons to be explicit). :-/

Best,
-- a.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-07-02 22:15:50 Re: Does TOAST really compress the complete row?
Previous Message Thomas Kellerer 2020-07-02 22:00:35 Does TOAST really compress the complete row?