| From: | Joe Conway <mail(at)joeconway(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | 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 17:25:56 |
| Message-ID: | 3CC05324.7080708@joeconway.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-04-19 17:35:11 | Re: Improved scanner performance |
| Previous Message | Peter Eisentraut | 2002-04-19 17:02:16 | Improved scanner performance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dmitry Tkach | 2002-04-19 17:31:43 | Patch for memory leaks in index scan |
| Previous Message | Tom Lane | 2002-04-19 16:57:49 | Re: Odd(?) RI-trigger behavior |