pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: pgsql-docs@lists.postgresql.org
Subject: Fix broken event trigger example
Date: Fri, 23 Dec 2022 13:10:10 +0100
Message-ID: <81e36ac17dc80489e74dc5b6914afa6ccdb1a99d.camel@cybertec.at> (raw)

The example in https://www.postgresql.org/docs/current/event-trigger-example.html
stopped compiling since commit 2f9661311b.

Here is a patch to fix that.

Yours,
Laurenz Albe

Attachments:

  [text/x-patch] 0001-Fix-event-trigger-example.patch (1.2K, ../81e36ac17dc80489e74dc5b6914afa6ccdb1a99d.camel@cybertec.at/2-0001-Fix-event-trigger-example.patch)
  download | inline diff:
From ae0aa8d01df0626a0417c6c339f59ee50de5c2b3 Mon Sep 17 00:00:00 2001
From: Laurenz Albe <laurenz.albe@cybertec.at>
Date: Fri, 23 Dec 2022 13:07:25 +0100
Subject: [PATCH] Fix event trigger example

Commit 2f9661311b changed command tags from strings to numbers,
but forgot to adjust the code in the event trigger example,
which consequently failed to compile.

While fixing that, improve the indentation to adhere to pgindent
style.

Backpatch to v13, where the change was introduced.

Author: Laurenz Albe
---
 doc/src/sgml/event-trigger.sgml | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/src/sgml/event-trigger.sgml b/doc/src/sgml/event-trigger.sgml
index f1235a2c9f..3b6a5361b3 100644
--- a/doc/src/sgml/event-trigger.sgml
+++ b/doc/src/sgml/event-trigger.sgml
@@ -1194,8 +1194,9 @@ noddl(PG_FUNCTION_ARGS)
     trigdata = (EventTriggerData *) fcinfo->context;
 
     ereport(ERROR,
-        (errcode(ERRCODE_INSUFFICIENT_PRIVILEGE),
-                 errmsg("command \"%s\" denied", trigdata->tag)));
+            (errcode(ERRCODE_INSUFFICIENT_PRIVILEGE),
+             errmsg("command \"%s\" denied",
+                    GetCommandTagName(trigdata->tag))));
 
     PG_RETURN_NULL();
 }
-- 
2.38.1



view thread (3+ messages)  latest in thread

Message-ID: <81e36ac17dc80489e74dc5b6914afa6ccdb1a99d.camel@cybertec.at>
Permalink:  ../81e36ac17dc80489e74dc5b6914afa6ccdb1a99d.camel@cybertec.at/
Also on:    postgresql.org/message-id/81e36ac17dc80489e74dc5b6914afa6ccdb1a99d.camel@cybertec.at

 ·  · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: laurenz.albe@cybertec.at, pgsql-docs@lists.postgresql.org
  Subject: Re: Fix broken event trigger example
  In-Reply-To: <81e36ac17dc80489e74dc5b6914afa6ccdb1a99d.camel@cybertec.at>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox