39P03 — event_trigger_protocol_violated

事件触发器辅助函数在错误的事件上下文调用。

英文手册覆盖始于 PostgreSQL 8.1. 来源历史与运行验证各自保留独立版本边界。

当前阅读 PG 18·选择有来源记录的版本

9.5 9.6 10 11 12 13 14 15 16 17 18 19 20

aliases: 未知
class name: External Routine Invocation Exception
condition name: event_trigger_protocol_violated
lang: en
sqlstate: 39P03

版本定义 PG 18

39P03

速览 {#at-a-glance}

39P03 是 event_trigger_protocol_violated。固定核心源码确认多个 event-trigger helper 会检查当前事件上下文。

含义 {#meaning}

调用 pg_event_trigger_dropped_objects()、table-rewrite helper 或 DDL helper 时，如果当前函数不是源码要求的 sql_drop、table_rewrite 或 event trigger function，就会报告该条件。固定报文中的 %s 会带出具体函数名；这属于调用上下文错误，不是对象不存在。

诊断 {#diagnosis}

先保留完整 message，确认被调用的 helper 以及实际 event trigger 类型。sql_drop、table_rewrite 和一般 event-trigger 上下文是不同边界；不要把这类错误解释成对象不存在或普通函数返回错误。

处置 {#response}

把 helper 调用放到匹配的 event trigger function 和事件中，或移除不适用的调用。核对部署版本的 event-trigger 定义与调用顺序后再重新执行 DDL；单纯重试原 DDL 不会改变当前上下文。

版本 {#versions}

锁定目录从 9.5.0 记录该条件，并在 9.5 之后的正式快照及 19beta3 中出现；固定报告该码的路径为 PostgreSQL 18.6。

来源 {#sources}

可直接阅读固定的 event_trigger.c helper 路径；完整范围见结构化证据记录。

比较版本

SQLSTATE 证据与已记录的运行版本

claims · identity

{
  "claim_id": "identity",
  "limits": "",
  "method": "Read the fixed definition row.",
  "position": 0,
  "runtime": [],
  "sources": [
    "src.errcodes.18.6"
  ],
  "statement": "39P03 is event_trigger_protocol_violated in Class 39."
}

claims · event-context

{
  "claim_id": "event-context",
  "limits": "",
  "method": "Read each currentEventTriggerState guard and its message.",
  "position": 1,
  "runtime": [],
  "sources": [
    "src.path.event-trigger"
  ],
  "statement": "The core event-trigger functions reject calls outside their required sql_drop, table_rewrite, or event-trigger context with this code."
}

claims · function-boundary

{
  "claim_id": "function-boundary",
  "limits": "",
  "method": "Compare the guard with the function named in the message.",
  "position": 2,
  "runtime": [],
  "sources": [
    "src.path.event-trigger"
  ],
  "statement": "The message names the required event-trigger function context, so the failing boundary is call context rather than object existence alone."
}

messages · message.sql-drop

{
  "limits": "",
  "message_id": "message.sql-drop",
  "path": "",
  "position": 0,
  "raw": {
    "id": "message.sql-drop",
    "primary_template": "%s can only be called in a sql_drop event trigger function",
    "severity_source": "ERROR",
    "sources": [
      "src.path.event-trigger"
    ],
    "sqlstate": "39P03"
  },
  "severity": "ERROR",
  "sources": [
    "src.path.event-trigger"
  ],
  "templates": [
    {
      "kind": "primary",
      "literal": "can only be called in a sql_drop event trigger function",
      "position": 0,
      "role": "",
      "template": "%s can only be called in a sql_drop event trigger function"
    }
  ]
}

messages · message.table-rewrite

{
  "limits": "",
  "message_id": "message.table-rewrite",
  "path": "",
  "position": 1,
  "raw": {
    "id": "message.table-rewrite",
    "primary_template": "%s can only be called in a table_rewrite event trigger function",
    "severity_source": "ERROR",
    "sources": [
      "src.path.event-trigger"
    ],
    "sqlstate": "39P03"
  },
  "severity": "ERROR",
  "sources": [
    "src.path.event-trigger"
  ],
  "templates": [
    {
      "kind": "primary",
      "literal": "can only be called in a table_rewrite event trigger function",
      "position": 0,
      "role": "",
      "template": "%s can only be called in a table_rewrite event trigger function"
    }
  ]
}

messages · message.event-trigger

{
  "limits": "",
  "message_id": "message.event-trigger",
  "path": "",
  "position": 2,
  "raw": {
    "id": "message.event-trigger",
    "primary_template": "%s can only be called in an event trigger function",
    "severity_source": "ERROR",
    "sources": [
      "src.path.event-trigger"
    ],
    "sqlstate": "39P03"
  },
  "severity": "ERROR",
  "sources": [
    "src.path.event-trigger"
  ],
  "templates": [
    {
      "kind": "primary",
      "literal": "can only be called in an event trigger function",
      "position": 0,
      "role": "",
      "template": "%s can only be called in an event trigger function"
    }
  ]
}

sources · src.errcodes.18.6

{
  "commit": "724edf9bde9d356724ad384a2e196edc3c9f80f7",
  "docs_url": "",
  "kind": "upstream_source",
  "location": "",
  "path": "src/backend/utils/errcodes.txt",
  "position": 0,
  "sha256": "6e8de346643ba84aa3c9c6a73360acfc7b2dfb89162c06c08ce9bf5bcd5bbcba",
  "source_id": "src.errcodes.18.6",
  "tag": "REL_18_6",
  "url": "https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/utils/errcodes.txt#L313"
}

sources · src.calls.REL_18_6

{
  "commit": "",
  "docs_url": "",
  "kind": "local_artifact",
  "location": "",
  "path": "raw/calls/REL_18_6.jsonl",
  "position": 1,
  "sha256": "9ee8a0e81d8f0825c5c1ae45583439859a26e602bdd4ce2f2a62aa278867ccbf",
  "source_id": "src.calls.REL_18_6",
  "tag": "",
  "url": ""
}

sources · src.path.event-trigger

{
  "commit": "724edf9bde9d356724ad384a2e196edc3c9f80f7",
  "docs_url": "",
  "kind": "upstream_source",
  "location": "",
  "path": "src/backend/commands/event_trigger.c",
  "position": 2,
  "sha256": "0c9d6c5da18411f63110aea40635cd82d8e1d591db5931ff37f3a52f53ee69eb",
  "source_id": "src.path.event-trigger",
  "tag": "REL_18_6",
  "url": "https://github.com/postgres/postgres/blob/724edf9bde9d356724ad384a2e196edc3c9f80f7/src/backend/commands/event_trigger.c#L1542-L1545"
}

来源引用

原始手册引用

完整定义与证据 JSON

定义来源

center · PostgreSQL 18 · english-manuals:8a70296194d2a159053ae04c00415ef245e36330805120f5a8ed3aafe4f2ac64

正文语言: zh-Hans · english-manuals:8a70296194d2a159053ae04c00415ef245e36330805120f5a8ed3aafe4f2ac64