Skip site navigation (1) Skip section navigation (2)

pgsql: Add pg_trigger_depth() function

From: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Add pg_trigger_depth() function
Date: 2012-01-25 16:24:24
Message-ID: E1Rq5e4-00039L-Bw@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Add pg_trigger_depth() function

This reports the depth level of triggers currently in execution, or zero
if not called from inside a trigger.

No catversion bump in this patch, but you have to initdb if you want
access to the new function.

Author: Kevin Grittner

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/74ab96a45ef6259aa6a86a781580edea8488511a

Modified Files
--------------
doc/src/sgml/func.sgml                 |    7 ++
src/backend/commands/trigger.c         |   21 ++++++-
src/include/catalog/pg_proc.h          |    3 +
src/include/commands/trigger.h         |    2 +
src/test/regress/expected/triggers.out |  117 ++++++++++++++++++++++++++++++++
src/test/regress/sql/triggers.sql      |   64 +++++++++++++++++
6 files changed, 213 insertions(+), 1 deletions(-)

pgsql-committers by date

Next:From: Simon RiggsDate: 2012-01-25 18:02:52
Subject: pgsql: Allow pg_basebackup from standby node with safety checking.
Previous:From: Bruce MomjianDate: 2012-01-25 14:35:29
Subject: pgsql: Now that the shared library name can be adjusted in thelibrary

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group