Content-Length: 14461 | pFad | https://postgr.es/m/tencent_083B3850655AC6EE04FA0A400766D3FE8309@qq.com

PostgreSQL: A Question about InvokeObjectPostAlterHook

A Question about InvokeObjectPostAlterHook

From: Legs Mansion <1027644833(at)qq(dot)com>
To: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: A Question about InvokeObjectPostAlterHook
Date: 2023-04-18 01:51:30
Message-ID: tencent_083B3850655AC6EE04FA0A400766D3FE8309@qq.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Recently, I ran into a problem, InvokeObjectPostAlterHook was implemented for sepgsql,
sepgsql use it to determine whether to check permissions during certain operations.
But InvokeObjectPostAlterHook doesn't handle all of the alter's behavior, at least the table is not controlled.&nbsp;e.g., ALTER TABLE... ENABLE/DISABLE ROW LEVEL SECURITY,ALTER TABLE ... DISABLE TRIGGER, GRANT and REVOKE and so on.
Whether InvokeObjectPostAlterHook&nbsp;is not fully controlled? it's a bug?

发自我的iPhone

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2023-04-18 02:06:43 Re: Fix typos and inconsistencies for v16
Previous Message Hayato Kuroda (Fujitsu) 2023-04-18 01:40:51 RE: pg_upgrade and logical replication








ApplySandwichStrip

pFad - (p)hone/(F)rame/(a)nonymizer/(d)eclutterfier!      Saves Data!


--- a PPN by Garber Painting Akron. With Image Size Reduction included!

Fetched URL: https://postgr.es/m/tencent_083B3850655AC6EE04FA0A400766D3FE8309@qq.com

Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy