| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Amit Langote <amitlangote09(at)gmail(dot)com> |
| 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-05-04 17:59:17 |
| Message-ID: | 20230504175917.vwq46sakb77tudyw@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2023-Mar-09, Amit Langote wrote:
> 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 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/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jonathan S. Katz | 2023-05-04 19:41:57 | Re: pg_stat_io not tracking smgrwriteback() is confusing |
| Previous Message | Jehan-Guillaume de Rorthais | 2023-05-04 17:30:06 | Re: Memory leak from ExecutorState context? |