Skip site navigation (1) Skip section navigation (2)


From: Richard Huxton <dev(at)archonet(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Lane <tgl(at)sss(dot)pgh(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-06 07:51:05
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-committerspgsql-hackers
Bruce Momjian wrote:
> 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.

Tom's point about triggers probably not working after the upgrade is a 
good one though. Is it reasonable to just refuse to act on a table until 
  all triggers are dropped? I'd rather be forced to go through and 
drop/restore triggers in a script than be surprised later on.

   Richard Huxton
   Archonet Ltd

In response to


pgsql-hackers by date

Next:From: Tony ReinaDate: 2004-05-06 08:22:45
Subject: Re: Function to do runtime relative directory mapping
Previous:From: Tatsuo IshiiDate: 2004-05-06 07:40:34
Subject: Re: PostgreSQL pre-fork speedup

pgsql-committers by date

Next:From: Tom LaneDate: 2004-05-06 14:01:33
Subject: pgsql-server/src backend/nodes/outfuncs.c back ...
Previous:From: Neil ConwayDate: 2004-05-06 06:11:01
Subject: pgsql-server/src/backend/nodes nodes.c

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group