Re: A bug with ExecCheckPermissions
Alvaro Herrera <alvherre@alvh.no-ip.org>
From: Alvaro Herrera <alvherre@alvh.no-ip.org>
To: Amit Langote <amitlangote09@gmail.com>
Cc: Sergey Shinderuk <s.shinderuk@postgrespro.ru>, o.tselebrovskiy@postgrespro.ru, pgsql-hackers@postgresql.org
Date: 2023-05-04T17:59:17Z
Lists: pgsql-hackers
On 2023-Mar-09, Amit Langote wrote: > On Thu, Mar 9, 2023 at 7:39 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote: > > I didn't like very much this business of setting the perminfoindex > > directly to '2' and '1'. It looks ugly with no explanation. What do > > you think of creating the as we go along and set each index > > correspondingly, as in the attached? > > Agree it looks cleaner and self-explanatory that way. Thanks. Thanks for looking! I have pushed it now. And many thanks to Oleg for noticing and reporting it. -- Álvaro Herrera 48°01'N 7°57'E — 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