| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)atentus(dot)com>, Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Odd(?) RI-trigger behavior |
| Date: | 2002-04-19 20:29:33 |
| Message-ID: | 3CC07E2D.7060601@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-19 20:36:33 | Re: Odd(?) RI-trigger behavior |
| Previous Message | Fernando Nasser | 2002-04-19 19:38:07 | Re: commands subdirectory continued -code cleanup |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-19 20:36:33 | Re: Odd(?) RI-trigger behavior |
| Previous Message | Dmitry Tkach | 2002-04-19 20:24:00 | Re: Patch for memory leaks in index scan |