From: | tgl(at)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql/ oc/src/sgml/ref/create_rule.sgml oc/src ... |
Date: | 2002-04-19 16:36:08 |
Message-ID: | 20020419163608.D70CB475971@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
CVSROOT: /cvsroot
Module name: pgsql
Changes by: tgl(at)postgresql(dot)org 02/04/19 12:36:08
Modified files:
doc/src/sgml/ref: create_rule.sgml create_trigger.sgml
doc/src/sgml : trigger.sgml
src/backend/catalog: indexing.c
src/backend/commands: comment.c tablecmds.c trigger.c
src/backend/utils/cache: relcache.c
src/include/catalog: catversion.h indexing.h
src/test/regress/expected: foreign_key.out
Log message:
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Vince Vielhaber | 2002-04-19 20:21:27 | [WEBMASTER] www/html/users-lounge |
Previous Message | Tom Lane | 2002-04-18 21:16:16 | pgsql/src/backend commands/user.c parser/gram. ... |