diff options
Diffstat (limited to 'doc/src')
| -rw-r--r-- | doc/src/sgml/event-trigger.sgml | 5 | ||||
| -rw-r--r-- | doc/src/sgml/func.sgml | 8 |
2 files changed, 11 insertions, 2 deletions
diff --git a/doc/src/sgml/event-trigger.sgml b/doc/src/sgml/event-trigger.sgml index d0306390346..cfa7b3d1b2d 100644 --- a/doc/src/sgml/event-trigger.sgml +++ b/doc/src/sgml/event-trigger.sgml @@ -104,6 +104,11 @@ control statements are available to rewrite a table, like <literal>CLUSTER</literal> and <literal>VACUUM</literal>, the <literal>table_rewrite</literal> event is not triggered by them. + To find the OID of the table that was rewritten, use the function + <literal>pg_event_trigger_table_rewrite_oid()</literal> (see + <xref linkend="functions-event-triggers"/>). To discover the reason(s) + for the rewrite, use the function + <literal>pg_event_trigger_table_rewrite_reason()</literal>. </para> <para> diff --git a/doc/src/sgml/func.sgml b/doc/src/sgml/func.sgml index 7be0324ac87..05f630c6a6c 100644 --- a/doc/src/sgml/func.sgml +++ b/doc/src/sgml/func.sgml @@ -31687,8 +31687,12 @@ CREATE EVENT TRIGGER test_event_trigger_for_drops <returnvalue>integer</returnvalue> </para> <para> - Returns a code explaining the reason(s) for rewriting. The exact - meaning of the codes is release dependent. + Returns a code explaining the reason(s) for rewriting. The value is + a bitmap built from the following values: <literal>1</literal> + (the table has changed its persistence), <literal>2</literal> + (default value of a column has changed), <literal>4</literal> + (a column has a new data type) and <literal>8</literal> + (the table access method has changed). </para></entry> </row> </tbody> |