| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | jian he <jian(dot)universality(at)gmail(dot)com> |
| Cc: | Daniel Gustafsson <daniel(at)yesql(dot)se>, Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: doc issues in event-trigger-matrix.html |
| Date: | 2024-10-29 11:54:03 |
| Message-ID: | e030642f-b6ae-4be9-8ac4-bbcad1361db9@eisentraut.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I made a patch for this. I have expanded the narrative discussion on
what commands are supported for event triggers, also made a few
corrections/additions there, based on inspecting the source code. And
then removed the big matrix, which doesn't provide any additional
information, I think.
I think this is sufficient and covers everything. The only hand-wavy
thing I can see is exactly which ALTER commands trigger the sql_drop
event. But this was already quite imprecise before, and I think also
not quite correct. This might need a separate investigation.
In any case, we can use this as a starting point to iterate on the right
wording etc.
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-doc-Remove-event-trigger-firing-matrix.patch | text/plain | 52.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2024-10-29 12:01:10 | [PATCH] Rename trim_array() for consistency with the rest of array_* functions |
| Previous Message | Shubham Khanna | 2024-10-29 11:38:50 | Re: Pgoutput not capturing the generated columns |