Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
Date
Msg-id 468843.1677533749@sss.pgh.pa.us
Whole thread Raw
In response to BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view  (PG Bug reporting form <noreply@postgresql.org>)
List pgsql-bugs
PG Bug reporting form <noreply@postgresql.org> writes:
> Maybe replacing a view with increasing number of columns should be
> prohibited too?

It's intentional that we allow that case; it'd be sad if we have
to remove the feature because of bugs.

            regards, tom lane



pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #17810: Update from 13.09 to 13.10 breaks SQLs with VACUUM
Next
From: Andrey Lepikhov
Date:
Subject: Re: Clause accidentally pushed down ( Possible bug in Making Vars outer-join aware)