| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Amit Langote <amitlangote09(at)gmail(dot)com> |
| Subject: | Re: Views no longer in rangeTabls? |
| Date: | 2023-06-09 09:04:55 |
| Message-ID: | 3c810344-94b3-19a6-26d0-e6350a0b811f@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 6/9/23 11:28, David Steele wrote:
>
> It seems the thing to do here would be to scan permInfos instead, which
> works fine except that we also need access to rellockmode, which is only
> included in rangeTabls. We can add a scan of rangeTabls to get
> rellockmode when needed and we might be better off overall since
> permInfos will generally have fewer entries. I have not implemented this
> yet but it seems like it will work.
I implemented this and it does work, but it was not as straight forward
as I would have liked. To make the relationship from RTEPermissionInfo
back to RangeTblEntry I was forced to generate my own perminfoindex.
This was not hard to do but seems a bit fragile. Perhaps we need an
rteindex in RTEPermissionInfo? This would also avoid the need to scan
rangeTabls.
Regards,
-David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2023-06-09 09:10:14 | Remove distprep |
| Previous Message | Richard Guo | 2023-06-09 08:57:02 | Re: Remove WindowClause PARTITION BY items belonging to redundant pathkeys |