From 73206812cd97436cffd8f331dbb09d38a2728162 Mon Sep 17 00:00:00 2001 From: Alvaro Herrera Date: Wed, 8 Apr 2015 15:26:50 -0300 Subject: Change SQLSTATE for event triggers "wrong context" message When certain event-trigger-only functions are called when not in the wrong context, they were reporting the "feature not supported" SQLSTATE, which is somewhat misleading. Create a new custom error code for such uses instead. Not backpatched since it may be seen as an undesirable behavioral change. Author: Michael Paquier Discussion: https://www.postgresql.org/message-id/CAB7nPqQ-5NAkHQHh_NOm7FPep37NCiLKwPoJ2Yxb8TDoGgbYYA@mail.gmail.com --- src/backend/utils/errcodes.txt | 1 + 1 file changed, 1 insertion(+) (limited to 'src/backend/utils') diff --git a/src/backend/utils/errcodes.txt b/src/backend/utils/errcodes.txt index 6a113b8f74c..6cc3ed96c44 100644 --- a/src/backend/utils/errcodes.txt +++ b/src/backend/utils/errcodes.txt @@ -278,6 +278,7 @@ Section: Class 39 - External Routine Invocation Exception 39004 E ERRCODE_E_R_I_E_NULL_VALUE_NOT_ALLOWED null_value_not_allowed 39P01 E ERRCODE_E_R_I_E_TRIGGER_PROTOCOL_VIOLATED trigger_protocol_violated 39P02 E ERRCODE_E_R_I_E_SRF_PROTOCOL_VIOLATED srf_protocol_violated +39P03 E ERRCODE_E_R_I_E_EVENT_TRIGGER_PROTOCOL_VIOLATED event_trigger_protocol_violated Section: Class 3B - Savepoint Exception -- cgit v1.2.3