> For the complete documentation index, see [llms.txt](https://docs.postgresql.tw/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.postgresql.tw/15/reference/sql-commands/drop-event-trigger.md).

# DROP EVENT TRIGGER

## DROP EVENT TRIGGER

DROP EVENT TRIGGER — remove an event trigger

### Synopsis

```

DROP EVENT TRIGGER [ IF EXISTS ] name [ CASCADE | RESTRICT ]
```

### Description

`DROP EVENT TRIGGER` removes an existing event trigger. To execute this command, the current user must be the owner of the event trigger.

### Parameters

`IF EXISTS`

Do not throw an error if the event trigger does not exist. A notice is issued in this case.

*`name`*

The name of the event trigger to remove.

`CASCADE`

Automatically drop objects that depend on the trigger, and in turn all objects that depend on those objects (see [Section 5.14](/15/the-sql-language/ddl/dependency-tracking.md)).

`RESTRICT`

Refuse to drop the trigger if any objects depend on it. This is the default.

### Examples

Destroy the trigger `snitch`:

```

DROP EVENT TRIGGER snitch;
```

### Compatibility

There is no `DROP EVENT TRIGGER` statement in the SQL standard.

### See Also

[CREATE EVENT TRIGGER](/15/reference/sql-commands/create-event-trigger.md), [ALTER EVENT TRIGGER](/15/reference/sql-commands/alter-event-trigger.md)

***

原文：[PostgreSQL 15.19 Documentation](/15/reference/sql-commands/drop-event-trigger.md)（英文原文，待翻譯）


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.postgresql.tw/15/reference/sql-commands/drop-event-trigger.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.