aboutsummaryrefslogtreecommitdiff
path: root/src/include/postgres_ext.h
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2024-10-29 15:35:01 +0900
committerMichael Paquier <michael@paquier.xyz>2024-10-29 15:35:01 +0900
commit4b7bba49e71266ec378e672a1aaa9f16823449c2 (patch)
tree27bc29ad66f64f218657ef0644738d347b3155e6 /src/include/postgres_ext.h
parentdda781609f977315c9ecdefc1e29f9499393aaa4 (diff)
downloadpostgresql-4b7bba49e71266ec378e672a1aaa9f16823449c2.tar.gz
postgresql-4b7bba49e71266ec378e672a1aaa9f16823449c2.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/include/postgres_ext.h')
0 files changed, 0 insertions, 0 deletions