<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Pg_trigger on Postgres Scripts</title><link>https://www.postgresscripts.com/tags/pg_trigger/</link><description>Recent content in Pg_trigger on Postgres Scripts</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>PostgresScripts.com</copyright><lastBuildDate>Sun, 07 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.postgresscripts.com/tags/pg_trigger/index.xml" rel="self" type="application/rss+xml"/><item><title>List All PostgreSQL Triggers with Their State</title><link>https://www.postgresscripts.com/post/list-all-postgresql-triggers-with-state-using-pg-trigger/</link><pubDate>Sun, 07 Jun 2026 00:00:00 +0000</pubDate><guid>https://www.postgresscripts.com/post/list-all-postgresql-triggers-with-state-using-pg-trigger/</guid><description>
&lt;h2 id="list-all-postgresql-triggers-with-their-state"&gt;List All PostgreSQL Triggers with Their State&lt;/h2&gt;
&lt;p&gt;A disabled trigger is invisible until something it should have done goes missing. The audit row that never got written, the derived column that stopped updating, the constraint check that silently stopped firing — each traces back to a trigger left in the disabled state after a bulk load or a restore. Listing files in &lt;code&gt;\d&lt;/code&gt; does not show this, but &lt;code&gt;pg_trigger.tgenabled&lt;/code&gt; does: one query returns every trigger across the database together with whether it actually fires.&lt;/p&gt;</description></item></channel></rss>