Re: A bug with ExecCheckPermissions

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Sergey Shinderuk <s(dot)shinderuk(at)postgrespro(dot)ru>, o(dot)tselebrovskiy(at)postgrespro(dot)ru, pgsql-hackers(at)postgresql(dot)org
Subject: Re: A bug with ExecCheckPermissions
Date: 2023-03-09 10:56:58
Message-ID: CA+HiwqFGgdBTJyOqmxatKyow=H5EdJUwsP=qx7c+OXJ6uLnWnw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi Alvaro,

On Thu, Mar 9, 2023 at 7:39 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)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, Amit Langote
EDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2023-03-09 11:20:37 Re: [PATCH] Use indexes on the subscriber when REPLICA IDENTITY is full on the publisher
Previous Message Alvaro Herrera 2023-03-09 10:45:30 Re: Small omission in type_sanity.sql