diff options
author | Michael Paquier <michael@paquier.xyz> | 2024-10-29 15:35:18 +0900 |
---|---|---|
committer | Michael Paquier <michael@paquier.xyz> | 2024-10-29 15:35:18 +0900 |
commit | a1b859c6893af2314fa29f8ac3c8bc8f3ad418e5 (patch) | |
tree | 02ea1ae7ab5f13327f6c3bb775a2d60348caf57a /src/backend/jit/llvm/SectionMemoryManager.cpp | |
parent | 4f47ee03d5f8adad0da40f650a165393b49cbcf1 (diff) | |
download | postgresql-a1b859c6893af2314fa29f8ac3c8bc8f3ad418e5.tar.gz postgresql-a1b859c6893af2314fa29f8ac3c8bc8f3ad418e5.zip |
doc: Add better description for rewrite functions in event triggers
There are two functions that can be used in event triggers to get more
details about a rewrite happening on a relation. Both had a limited
documentation:
- pg_event_trigger_table_rewrite_reason() and
pg_event_trigger_table_rewrite_oid() were not mentioned in the main
event trigger section in the paragraph dedicated to the event
table_rewrite.
- pg_event_trigger_table_rewrite_reason() returns an integer which is a
bitmap of the reasons why a rewrite happens. There was no explanation
about the meaning of these values, forcing the reader to look at the
code to find out that these are defined in event_trigger.h.
While on it, let's add a comment in event_trigger.h where the
AT_REWRITE_* are defined, telling to update the documentation when
these values are changed.
Backpatch down to 13 as a consequence of 1ad23335f36b, where this area
of the documentation has been heavily reworked.
Author: Greg Sabino Mullane
Discussion: https://postgr.es/m/CAKAnmmL+Z6j-C8dAx1tVrnBmZJu+BSoc68WSg3sR+CVNjBCqbw@mail.gmail.com
Backpatch-through: 13
Diffstat (limited to 'src/backend/jit/llvm/SectionMemoryManager.cpp')
0 files changed, 0 insertions, 0 deletions