Re: Odd(?) RI-trigger behavior - Mailing list pgsql-hackers

From Joe Conway
Subject Re: Odd(?) RI-trigger behavior
Date
Msg-id 3CC07E2D.7060601@joeconway.com
Whole thread Raw
In response to Re: Odd(?) RI-trigger behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Odd(?) RI-trigger behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Joe Conway wrote:
> Tom Lane wrote:
> 
>>
>> Yeah.  As of CVS tip, to reshuffle the order of existing triggers you
>> must (a) do a manual UPDATE pg_trigger SET tgname = 'something' ...
>> then (b) restart your backend(s), because the relcache code does not
>> notice that you did that, so it'll keep using the trigger data it
>> already had loaded.  This is pretty ugly.  An ALTER TRIGGER command
>> seems called for if we want to call the TODO item really done.
>> I haven't got time for that at the moment; any volunteers?
>>
> 
> I'll take it.
> 

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?


Joe




pgsql-hackers by date:

Previous
From: Fernando Nasser
Date:
Subject: Re: commands subdirectory continued -code cleanup
Next
From: Tom Lane
Date:
Subject: Re: Odd(?) RI-trigger behavior