pg_event_trigger_ddl_commands after GRANT is quite empty
pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
Дата:
Dear Postgres Community,
pg_event_trigger_ddl_commands after GRANT is quite empty.
If I execute: GRANT SELECT ON TABLE t TO r;
. and in a trigger function I have:
SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity
FROM pg_event_trigger_ddl_commands();
This gives me:
null, null, null, GRANT, TABLE, null, null
How to find out the table involved and the privileges?
Regards,
Franz-Josef Färber
Re: pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Adrian Klaver <adrian.klaver@aklaver.com>
Дата:
On 10/12/26 1:47 AM, Färber, Franz-Josef (StMUK) wrote: > Dear Postgres Community, > > pg_event_trigger_ddl_commands after GRANT is quite empty. > > If I execute: GRANT SELECT ON TABLE t TO r; > > . and in a trigger function I have: > > SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity > FROM pg_event_trigger_ddl_commands(); > > This gives me: > > null, null, null, GRANT, TABLE, null, null > Postgres version? What is the complete trigger and trigger function definition? > > How to find out the table involved and the privileges? > > > Regards, > Franz-Josef Färber > > -- Adrian Klaver adrian.klaver@aklaver.com
Re: pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Laurenz Albe <laurenz.albe@cybertec.at>
Дата:
On Mon, 2026-10-12 at 08:47 +0000, Färber, Franz-Josef (StMUK) wrote: > pg_event_trigger_ddl_commands after GRANT is quite empty. > > If I execute: GRANT SELECT ON TABLE t TO r; > > . and in a trigger function I have: > > SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity > FROM pg_event_trigger_ddl_commands(); > > This gives me: > > null, null, null, GRANT, TABLE, null, null > > > How to find out the table involved and the privileges? I think you have to write a C function that can do something with pg_ddl_command. Yours, Laurenz Albe
AW: pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
Дата:
Thanks! A solution usable from SQL or plpgsql would've been nice. Regards, Franz-Josef Färber -----Ursprüngliche Nachricht----- Von: Laurenz Albe Gesendet: Montag, 12. Oktober 2026 16:27 An: Färber, Franz-Josef (StMUK) ; pgsql-general@postgresql.org Betreff: Re: pg_event_trigger_ddl_commands after GRANT is quite empty On Mon, 2026-10-12 at 08:47 +0000, Färber, Franz-Josef (StMUK) wrote: > pg_event_trigger_ddl_commands after GRANT is quite empty. > > If I execute: GRANT SELECT ON TABLE t TO r; > > . and in a trigger function I have: > > SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity > FROM pg_event_trigger_ddl_commands(); > > This gives me: > > null, null, null, GRANT, TABLE, null, null > > > How to find out the table involved and the privileges? I think you have to write a C function that can do something with pg_ddl_command. Yours, Laurenz Albe
AW: pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Färber, Franz-Josef (StMUK) <Franz-Josef.Faerber@stmuk.bayern.de>
Дата:
SELECT version();
--PostgreSQL 18.6 (Debian 18.6-1.pgdg13+2) on x86_64-pc-linux-gnu, compiled by gcc (Debian 14.2.0-19) 14.2.0, 64-bit
CREATE FUNCTION ddl_command_end_trigger_func() RETURNS event_trigger
LANGUAGE plpgsql
AS $$
BEGIN
RAISE NOTICE USING MESSAGE = (
SELECT concat_ws(', ', classid, objid, objsubid, command_tag, object_type, schema_name, object_identity)
FROM pg_event_trigger_ddl_commands()
);
END
$$;
CREATE EVENT TRIGGER ddl_command_end_trigger ON ddl_command_end EXECUTE FUNCTION ddl_command_end_trigger_func();
CREATE TABLE t();
GRANT SELECT ON TABLE t TO postgres;
Regards,
Franz-Josef Färber
-----Ursprüngliche Nachricht-----
Von: Adrian Klaver
Gesendet: Montag, 12. Oktober 2026 16:18
An: Färber, Franz-Josef (StMUK) ; pgsql-general@postgresql.org
Betreff: Re: pg_event_trigger_ddl_commands after GRANT is quite empty
On 10/12/26 1:47 AM, Färber, Franz-Josef (StMUK) wrote:
> Dear Postgres Community,
>
> pg_event_trigger_ddl_commands after GRANT is quite empty.
>
> If I execute: GRANT SELECT ON TABLE t TO r;
>
> . and in a trigger function I have:
>
> SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity
> FROM pg_event_trigger_ddl_commands();
>
> This gives me:
>
> null, null, null, GRANT, TABLE, null, null
>
Postgres version?
What is the complete trigger and trigger function definition?
>
> How to find out the table involved and the privileges?
>
>
> Regards,
> Franz-Josef Färber
>
>
--
Adrian Klaver
adrian.klaver@aklaver.com
Re: AW: pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Laurenz Albe <laurenz.albe@cybertec.at>
Дата:
On Mon, 2026-10-12 at 14:36 +0000, Färber, Franz-Josef (StMUK) wrote: > > > pg_event_trigger_ddl_commands after GRANT is quite empty. > > > > > > If I execute: GRANT SELECT ON TABLE t TO r; > > > > > > . and in a trigger function I have: > > > > > > SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity > > > FROM pg_event_trigger_ddl_commands(); > > > > > > This gives me: > > > > > > null, null, null, GRANT, TABLE, null, null > > > > > > > > > How to find out the table involved and the privileges? > > > > I think you have to write a C function that can do something with pg_ddl_command. > > A solution usable from SQL or plpgsql would've been nice. Indeed. I am surprised that the table is not reported for a GRANT statement. Perhaps it is because GRANT operates on all kinds of objects, not sure. You could write a patch for PostgreSQL to improve that. Yours, Laurenz Albe
Re: pg_event_trigger_ddl_commands after GRANT is quite empty
От:
Álvaro Herrera <alvherre@kurilemu.de>
Дата:
On 2026-Oct-12, Färber, Franz-Josef (StMUK) wrote: > Dear Postgres Community, > > pg_event_trigger_ddl_commands after GRANT is quite empty. > > If I execute: GRANT SELECT ON TABLE t TO r; > > . and in a trigger function I have: > > SELECT classid, objid, objsubid, command_tag, object_type, schema_name, object_identity > FROM pg_event_trigger_ddl_commands(); > > This gives me: > > null, null, null, GRANT, TABLE, null, null > > How to find out the table involved and the privileges? Yeah, I'm afraid the implementation to expose this to SQL was left incomplete back in 9.5. You can see in EventTriggerCollectGrant() that we do try and collect the information, but in pg_event_trigger_ddl_commands() in event_trigger.c the case for SCT_Grant fills nulls for most columns. The CollectedCommand pointer is present and should contain all details of the grant, though, so as Laurenz says you can get by in the meantime with some C code. Exposing it in SQL (which we're likely to require now that Sawada-san is back at implementing DDL replication) is going to require some additional design for the datatypes and so on. The difference between GRANT and all others is that you affect multiple objects and multiple privileges in a single command, so we cannot just shoehorn an object name in the same place as for the other commands. One weird thing I noticed is that there isn't a single GRANT in the tests in src/test/modules/test_ddl_deparse. But that wouldn't have changed things at all, I'm afraid ... (You could use the code there as a template to implement your own, BTW.) -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/