RENAME TRIGGER patch (was [HACKERS] Odd(?) RI-trigger behavior)

Tom Lane wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>
>> There is already a RenameStmt node which is currently only used to
>> rename tables or table column names. Is there any objection to
>> modifying it to handle trigger names (and possibly other things in
>> the future) also?
>
>
> You'd need to add a field so you could distinguish the type of
> rename, but on the whole that seems a reasonable thing to do;
> probably better than adding a brand new node type. We're already
> sharing node types for DROPs, for example, so I see no reason not to
> do it for RENAMEs. (Cf 'DropPropertyStmt' in current sources)
>
> Renaming rules seems like something that should be on the list too, so
> you're right that there will be more stuff later.
>

Attached is a patch for ALTER TRIGGER RENAME per the above thread. I
left a stub for a future "ALTER RULE RENAME" but did not write that one
yet. Bruce, if you want to add my name for for that I'll take it and do
it later.

It passes all regression tests on my RH box. Usage is as follows:

test=# create table foo3(f1 int references foo2(f1));
NOTICE: CREATE TABLE will create implicit trigger(s) for FOREIGN KEY
check(s)
CREATE
test=# \d foo3
Table "foo3"
Column | Type | Modifiers
--------+---------+-----------
f1 | integer |
Triggers: RI_ConstraintTrigger_16663

test=# alter trigger "RI_ConstraintTrigger_16663" on foo3 rename to
"MyOwnConstTriggerName";
ALTER
test=# \d foo3
Table "foo3"
Column | Type | Modifiers
--------+---------+-----------
f1 | integer |
Triggers: MyOwnConstTriggerName

Obviously there is no build in restriction on altering the name of
refint triggers -- is this a problem?

I'll follow up with a doc patch this weekend. If there are no
objections, please apply.

Thanks,

Joe