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

From Joe Conway
Subject Re: Odd(?) RI-trigger behavior
Date
Msg-id 3CC05324.7080708@joeconway.com
Whole thread Raw
In response to Re: Odd(?) RI-trigger behavior  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.

Joe



pgsql-hackers by date:

Previous
From: Barry Lind
Date:
Subject: Re: Large object security
Next
From: Tom Lane
Date:
Subject: Re: Improved scanner performance