Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: exclusion@gmail.com
Cc: pgsql-bugs@lists.postgresql.org
Date: 2023-02-27T21:35:49Z
Lists: 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
Commits
-
Fix more bugs caused by adding columns to the end of a view.
- 99be6feec971 16.0 landed
- 76d2177fb693 15.3 landed
- 9f1e51b59673 14.8 landed
- 721626cb57c0 11.20 landed
- 695b34ab359d 13.11 landed
- 5a19da58eed2 12.15 landed
-
Fix crash when columns have been added to the end of a view.
- d5b760ecb5e1 11.0 cited