The message returned if the trigger is successfully dropped.
</PARA>
</LISTITEM>
</VARLISTENTRY>
<VARLISTENTRY>
<TERM>
<ReturnValue>ERROR: DropTrigger: there is no trigger <REPLACEABLE CLASS="PARAMETER">name</REPLACEABLE> on relation "<replaceable class="parameter">table</replaceable>"</ReturnValue>
</TERM>
<LISTITEM>
<PARA>
This message occurs if the trigger specified does not exist.
</PARA>
</LISTITEM>
</VARLISTENTRY>
</variablelist>
</LISTITEM>
</VARLISTENTRY>
</VARIABLELIST>
</REFSECT2>
</REFSYNOPSISDIV>
<REFSECT1 ID="R1-SQL-DROPTRIGGER-1">
<REFSECT1INFO>
<DATE>1998-04-15</DATE>
</REFSECT1INFO>
<TITLE>
Description
</TITLE>
<PARA>
<command>DROP TRIGGER</command> will remove all references to an existing
trigger definition. To execute this command the current
user must be the owner of the trigger.
</PARA>
<REFSECT2 ID="R2-SQL-DROPTRIGGER-3">
<REFSECT2INFO>
<DATE>1998-04-15</DATE>
</REFSECT2INFO>
<TITLE>
Notes
</TITLE>
<PARA>
The <command>DROP TRIGGER</command> statement is a PostgreSQL
language extension.
</PARA>
<PARA>
Refer to the <command>CREATE TRIGGER</command> statement for
information on how to create triggers.
</PARA>
</REFSECT2>
<REFSECT1 ID="R1-SQL-DROPTRIGGER-2">
<TITLE>
Usage
</TITLE>
<PARA>
Destroy the <literal>if_dist_exists</literal> trigger on table <literal>films</literal>:
</PARA>
<ProgramListing>
DROP TRIGGER if_dist_exists ON films;
</ProgramListing>
</REFSECT1>
<REFSECT1 ID="R1-SQL-DROPTRIGGER-3">
<TITLE>
Compatibility
</TITLE>
<PARA>
</PARA>
<REFSECT2 ID="R2-SQL-DROPTRIGGER-4">
<REFSECT2INFO>
<DATE>1998-04-15</DATE>
</REFSECT2INFO>
<TITLE>
SQL92
</TITLE>
<PARA>
There is no <command>DROP TRIGGER</command> statement in SQL92.