Re: ALTER TABLE TODO items

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Richard Huxton <dev(at)archonet(dot)com>
Cc: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER TABLE TODO items
Date: 2004-05-05 19:50:02
Message-ID: 9389.1083786602@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Richard Huxton <dev(at)archonet(dot)com> writes:
> Does that mean I'll want to disable triggers while I do this?

Hrm. Right now the code does not fire triggers at all, but that seems
wrong. However, I doubt that very many triggers could cope with update
events in which the old and new rows have different rowtypes :-(.
Any thoughts what to do about that?

regards, tom lane

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2004-05-05 21:18:30 pgsql-server/ /configure /configure.in rc/bin/ ...
Previous Message Richard Huxton 2004-05-05 19:45:39 Re: ALTER TABLE TODO items

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-05-05 19:53:53 Re: initdb failure in CVS
Previous Message Richard Huxton 2004-05-05 19:45:39 Re: ALTER TABLE TODO items