From: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
---|---|
To: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: doc issues in event-trigger-matrix.html |
Date: | 2024-03-21 22:10:37 |
Message-ID: | 0C0F3257-4DD5-461D-8C23-CA735D301C94@yesql.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> On 21 Mar 2024, at 22:47, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> On 19.03.24 10:34, Daniel Gustafsson wrote:
>>>> "Only for local objects"
>>>> is there any reference explaining "local objects"?
>>>> I think local object means objects that only affect one single database?
>> That's a bigger problem than the table representation, we never define what
>> "local object" mean anywhere in the EVT docs. EV's are global for a database,
>> but not a cluster, so I assume what this means is that EVs for non-DDL commands
>> like COMMENT can only fire for a specific relation they are attached to and not
>> database wide?
>
> I think we could replace this whole table by a few definitions:
Simply extending the "Overview of Event Trigger Behavior" section slightly
might even be enough?
> If tomorrow someone changes ... will they remember to update this table?
Highly unlikely.
--
Daniel Gustafsson
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2024-03-21 22:20:05 | Re: Adding comments to help understand psql hidden queries |
Previous Message | Peter Eisentraut | 2024-03-21 22:08:10 | Re: Refactoring of pg_resetwal/t/001_basic.pl |