Re: pg_upgrade failed if view contain natural left join condition
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: tushar <tushar.ahuja@enterprisedb.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2017-07-20T13:53:23Z
Lists: 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
Commits
-
Doc: clarify description of degenerate NATURAL joins.
- 80af818dd618 9.2.22 landed
- a6088e1f5a58 9.3.18 landed
- 769eaef7600b 9.4.13 landed
- 315ca7ffb909 9.5.8 landed
- 5512427b19e7 9.6.4 landed
- ed3dc224e5aa 10.0 landed
-
Fix dumping of outer joins with empty qual lists.
- eb145fdfea91 10.0 landed
- e947838ae432 9.3.18 landed
- c2bbec9f2b36 9.5.8 landed
- 6ab4a1136ed9 9.4.13 landed
- 41ada8377492 9.6.4 landed