From 5fce30e77fe133e1404167c13caaf7e0d1369295 Mon Sep 17 00:00:00 2001 From: Alexander Korotkov Date: Mon, 12 Feb 2024 00:33:51 +0200 Subject: [PATCH] Fix some typos in event trigger docs Discussion: https://postgr.es/m/CALj2ACWFUW4jX9EW7CLxbzSS%2Bb7b0Z%3DxKYrqzj2Rstc9MCEx7g%40mail.gmail.com Author: Bharath Rupireddy --- doc/src/sgml/event-trigger.sgml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/doc/src/sgml/event-trigger.sgml b/doc/src/sgml/event-trigger.sgml index a76bd844257..23dbb804819 100644 --- a/doc/src/sgml/event-trigger.sgml +++ b/doc/src/sgml/event-trigger.sgml @@ -49,7 +49,7 @@ To prevent servers from becoming inaccessible, such triggers must avoid writing anything to the database when running on a standby. Also, it's recommended to avoid long-running queries in - login event triggers. Notes that, for instance, + login event triggers. Note that, for instance, canceling connection in psql wouldn't cancel the in-progress login trigger. @@ -1144,8 +1144,9 @@ typedef struct EventTriggerData Describes the event for which the function is called, one of - "ddl_command_start", "ddl_command_end", - "sql_drop", "table_rewrite". + "login", "ddl_command_start", + "ddl_command_end", "sql_drop", + "table_rewrite". See for the meaning of these events. @@ -1203,8 +1204,9 @@ typedef struct EventTriggerData This is the source code of the trigger function: