From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
Date: Mon, 27 Feb 2023 16:35:49 -0500
Message-ID: <468843.1677533749@sss.pgh.pa.us> (raw)
In-Reply-To: <17811-d31686b78f0dffc9@postgresql.org>
References: <17811-d31686b78f0dffc9@postgresql.org>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, exclusion@gmail.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
In-Reply-To: <468843.1677533749@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox