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

From Alexander Lakhin
Subject Re: BUG #17811: Replacing an underlying view breaks OLD/NEW tuple when accessing it via upper-level view
Date
Msg-id b941ef12-c466-2eee-c3d4-f3c882ec0d16@gmail.com
Whole thread Raw
In response to 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>)
List pgsql-bugs
07.03.2023 21:43, Tom Lane wrote:
> I've looked into this a bit more, and both of these symptoms reduce
> to the same thing: after we've plugged the modified view's query
> into the upper query, we have an RTE_SUBQUERY RTE whose eref->colnames
> list is shorter than the number of columns actually available from the
> subquery.  This breaks assorted code that is expecting that it can
> use list_length(eref->colnames) as a quick guide to the number of
> output columns.

Thanks for the fix!
I've tested all my cases on REL_15_STABLE, master and found no
anomalies in this area.

Best regards,
Alexander



pgsql-bugs by date:

Previous
From: Jeff Davis
Date:
Subject: unaccent fails when datlocprovider=i and datctype=C
Next
From: Francisco Olarte
Date:
Subject: Re: pg_basebackup fails with Could not stat file or directory "./.pg_hba.conf.un~"