Re: on placeholder entries in view rule action query's range table
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Amit Langote <amitlangote09@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, Alvaro Herrera <alvherre@alvh.no-ip.org>,
PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2023-04-05T18:33:33Z
Lists: pgsql-hackers
Amit Langote <amitlangote09@gmail.com> writes: > While thinking about query view locking in context of [1], I realized > that we have missed also fixing AcquirePlannerLocks() / > ScanQueryForLocks() to consider that an RTE_SUBQUERY rte may belong to > a view, which must be locked the same as RTE_RELATION entries. I think you're right about that, because AcquirePlannerLocks is supposed to reacquire whatever locks parsing+rewriting would have gotten. However, what's with this hunk? @@ -527,7 +527,7 @@ standard_planner(Query *parse, const char *query_string, int cursorOptions, result->partPruneInfos = glob->partPruneInfos; result->rtable = glob->finalrtable; result->permInfos = glob->finalrteperminfos; - result->viewRelations = glob->viewRelations; + result->viewRelations = NIL; result->resultRelations = glob->resultRelations; result->appendRelations = glob->appendRelations; result->subplans = glob->subplans; regards, tom lane
Commits
-
Acquire locks on views in AcquirePlannerLocks, too.
- 65eb2d00c6c1 16.0 landed
-
Get rid of the "new" and "old" entries in a view's rangetable.
- 47bb9db75996 16.0 landed
- 1b4d280ea1eb 16.0 landed
-
vacuumlazy.c: Save get_database_name() in vacrel.
- 54afdcd6182a 16.0 cited