From: | David Steele <david(at)pgmasters(dot)net> |
---|---|
To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Julien Rouhaud <rjuju123(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Views no longer in rangeTabls? |
Date: | 2023-06-13 08:57:36 |
Message-ID: | 2b53d137-1448-44cb-11fd-11319cfcb4da@pgmasters.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 6/13/23 10:27, Amit Langote wrote:
> On Tue, Jun 13, 2023 at 4:44 PM David Steele <david(at)pgmasters(dot)net> wrote:
>
>> I decided to go with the following because I think it
>> is easier to read:
>>
>> /* We only care about tables/views and can ignore subqueries, etc. */
>> if (!(rte->rtekind == RTE_RELATION ||
>> (rte->rtekind == RTE_SUBQUERY && rte->relkind == RELKIND_VIEW)))
>> continue;
>
> It didn't occur to me so far to mention it but this could be replaced with:
>
> if (rte->perminfoindex != 0)
>
> and turn that condition into an Assert instead, like the loop over
> range table in ExecCheckPermissions() does.
Hmmm, that might work, and save us a filter on rte->perminfoindex later
on (to filter out table partitions). Thanks for the tip!
>>> I considered adding Assert(relkind == RELKIND_VIEW) in all places that
>>> have the "rte->rtekind == RTE_SUBQUERY && OidIsValid(rte->relid)"
>>> condition, but that seemed like an overkill, so only added one in the
>>> #ifdef USE_ASSERT_CHECKING block in ExecCheckPermissions() that
>>> f75cec4fff877 added.
>>
>> This seems like a good place for the assert.
>
> I added a comment above this Assert.
>
> I'd like to push this tomorrow barring objections.
+1 for the new comment.
Regards,
-David
From | Date | Subject | |
---|---|---|---|
Next Message | Amit Kapila | 2023-06-13 08:59:05 | Re: Non-superuser subscription owners |
Previous Message | Amit Kapila | 2023-06-13 08:55:50 | Re: Non-superuser subscription owners |