Re: Views no longer in rangeTabls?
Julien Rouhaud <rjuju123@gmail.com>
From: Julien Rouhaud <rjuju123@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: David Steele <david@pgmasters.net>, Amit Langote <amitlangote09@gmail.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2023-06-10T13:18:57Z
Lists: pgsql-hackers
On Sat, Jun 10, 2023 at 08:56:47AM -0400, Tom Lane wrote: > > Well, if we're gonna do it we should do it for v16, rather than > change the data structure twice. It wouldn't be hard exactly: > > /* > * Clear fields that should not be set in a subquery RTE. Note that we > * leave the relid, rellockmode, and perminfoindex fields set, so that the > * view relation can be appropriately locked before execution and its > * permissions checked. > */ > - rte->relkind = 0; > rte->tablesample = NULL; > rte->inh = false; /* must not be set for a subquery */ > > plus adjustment of that comment and probably also the comment > for struct RangeTblEntry. and also handle that field in (read|out)funcs.c
Commits
-
Retain relkind too in RTE_SUBQUERY entries for views.
- 0f8cfaf8921f 16.0 landed