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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: exclusion(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
Date: 2023-02-27 21:35:49
Message-ID: 468843.1677533749@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Browse pgsql-bugs by date

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