Re: [HACKERS] pg_upgrade failed if view contain natural left join condition - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] pg_upgrade failed if view contain natural left join condition
Date
Msg-id 7383.1500558803@sss.pgh.pa.us
Whole thread Raw
In response to [HACKERS] pg_upgrade failed if view contain natural left join condition  (tushar <tushar.ahuja@enterprisedb.com>)
Responses Re: [HACKERS] pg_upgrade failed if view contain natural left join condition
List pgsql-hackers
tushar <tushar.ahuja@enterprisedb.com> writes:
> postgres=# create table t(n int);
> CREATE TABLE
> postgres=# create table t1(a int);
> CREATE TABLE
> postgres=# create view ttt1 as SELECT e.n FROM t e NATURAL LEFT JOIN t1 d;
> CREATE VIEW

You realize of course that that's a pretty useless join definition.
Still, yes, we do need to reverse-list the view with correct syntax.
Probably t LEFT JOIN t1 ON TRUE would do it.

> I think -this issue should be there in the older branches as well but 
> not checked that.

[experiments]  Seems to be wrong back to 9.3.  Although I have a feeling
this might be a mistake in a back-patched bug fix, so that it'd depend
on which 9.3.x you looked at.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] pg_upgrade failed if view is based on sequence
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Cache lookup errors with functions manipulation object addresses