OSDN Git Service

pg_trigger's index on tgrelid is replaced by a unique index on
authorTom Lane <tgl@sss.pgh.pa.us>
Fri, 19 Apr 2002 16:36:08 +0000 (16:36 +0000)
committerTom Lane <tgl@sss.pgh.pa.us>
Fri, 19 Apr 2002 16:36:08 +0000 (16:36 +0000)
commit201737168c4ed5b14313d111d8d746c7f072f24e
tree4936cf1082506bbf110dbf49d7e219f92e729c0d
parent87d00363cb46aa5f69ec4ed7874c356a0db8f25a
pg_trigger's index on tgrelid is replaced by a unique index on
(tgrelid, tgname).  This provides an additional check on trigger name
uniqueness per-table (which was already enforced by the code anyway).
With this change, RelationBuildTriggers will read the triggers in
order by tgname, since it's scanning using this index.  Since a
predictable trigger ordering has been requested for some time, document
this behavior as a feature.  Also document that rules fire in name
order, since yesterday's changes to pg_rewrite indexing cause that too.
doc/src/sgml/ref/create_rule.sgml
doc/src/sgml/ref/create_trigger.sgml
doc/src/sgml/trigger.sgml
src/backend/catalog/indexing.c
src/backend/commands/comment.c
src/backend/commands/tablecmds.c
src/backend/commands/trigger.c
src/backend/utils/cache/relcache.c
src/include/catalog/catversion.h
src/include/catalog/indexing.h
src/test/regress/expected/foreign_key.out