Re: A bug with ExecCheckPermissions
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: o.tselebrovskiy@postgrespro.ru
Cc: pgsql-hackers@postgresql.org, s.shinderuk@postgrespro.ru, Amit Langote <amitlangote09@gmail.com>
Date: 2023-02-08T10:49:00Z
Lists: pgsql-hackers
On 2023-Feb-08, o.tselebrovskiy@postgrespro.ru wrote: > But if you debug function ExecCheckPermissions and look into what is passed > to function (contents of rangeTable and rteperminfos to be exact), > you'll see some strange behaviour: > Both of RangeTableEntries have a perminfoindex of 0 and simultaneously have > a RTEPERMISSIONINFO entry for them! Ouch. Yeah, that's not great. As you say, it doesn't really affect anything, and we know full well that these RTEs are ad-hoc manufactured. But as we claim that we still pass the RTEs for the benefit of hooks, then we should at least make them match. I think we should also patch ExecCheckPermissions to use forboth(), scanning the RTEs as it goes over the perminfos, and make sure that the entries are consistent. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
Commits
-
Fix sepgsql expected test output
- 95f5a7a42c04 16.0 landed
-
Fix ExecCheckPermissions call in RI_Initial_Check
- f75cec4fff87 16.0 landed