Tom Lane wrote:
> 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?
If triggers exist, I think we should just throw a warning that triggers
will not be fired.
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
In response to
pgsql-hackers by date
|Next:||From: sdv mailer||Date: 2004-05-06 04:29:55|
|Subject: Re: PostgreSQL pre-fork speedup|
|Previous:||From: Bruce Momjian||Date: 2004-05-06 02:49:45|
|Subject: Re: Multiple Xids in PGPROC?|
pgsql-committers by date
|Next:||From: Neil Conway||Date: 2004-05-06 06:11:01|
|Subject: pgsql-server/src/backend/nodes nodes.c|
|Previous:||From: Christopher Kings-Lynne||Date: 2004-05-06 01:45:03|
|Subject: Re: ALTER TABLE TODO items|