projects / users / hanada / postgres.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: dd21f0b) | patch
Use only one hash entry for all instances of a pltcl trigger function.
authorTom Lane <tgl@sss.pgh.pa.us>
Wed, 3 Nov 2010 16:26:55 +0000 (12:26 -0400)
committerTom Lane <tgl@sss.pgh.pa.us>
Wed, 3 Nov 2010 16:26:55 +0000 (12:26 -0400)
commit70a0160b07b66dc7fa1555c489330ea8fb58f8fe
tree6a01c5e3a8b809b87f48a95c784f37c0d3e3bbd9tree
parentdd21f0b047078ae724c0de4bc87b175154a83707commit | diff
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
src/pl/tcl/pltcl.c diff | blob | blame | history
Hanada's development tree.