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

pgsql: Use only one hash entry for all instances of a pltcl triggerfun

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Use only one hash entry for all instances of a pltcl triggerfun
Date: 2010-11-03 16:27:22
Message-ID: E1PDgBG-00018F-LK@gemulon.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-committers
Use only one hash entry for all instances of a pltcl trigger function.

Like plperl and unlike plpgsql, there isn't any cached state that could
depend on exactly which relation the trigger is being fired for.  So we
can use just one hash entry for all relations, which might save a little
something.

Alex Hunsaker

Branch
------
master

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=70a0160b07b66dc7fa1555c489330ea8fb58f8fe

Modified Files
--------------
src/pl/tcl/pltcl.c |   16 +++++++++++-----
1 files changed, 11 insertions(+), 5 deletions(-)

pgsql-committers by date

Next:From: Tom LaneDate: 2010-11-03 17:42:59
Subject: pgsql: Reduce recursion depth in recently-added regression test.
Previous:From: Peter EisentrautDate: 2010-11-03 15:33:42
Subject: pgsql: Print a make warning when using GNU make older than 3.80

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