ALTER TABLE ... DISABLE TRIGGERS Isolation leve - Mailing list pgsql-general

From CG
Subject ALTER TABLE ... DISABLE TRIGGERS Isolation leve
Date
Msg-id 577889.30680.qm@web37906.mail.mud.yahoo.com
Whole thread Raw
Responses Re: ALTER TABLE ... DISABLE TRIGGERS Isolation leve  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
I'm using 8.4.1

I want to add a column to a table, but there are update triggers that will fire that don't need to fire for this
operation.So, I'd like to add the column with triggers off. Normally this operation would take 10 or so seconds, so
lockingthe table for that amount of time is not a big deal. I just want to make sure that no new data gets written to
thetable while the triggers are disabled. 

BEGIN;
ALTER TABLE foo ADD COLUMN bar DISABLE TRIGGER USER;
COMMIT;

seems to leave the triggers disabled.

My tests seem to show that


BEGIN;
ALTER TABLE foo DISABLE TRIGGER USER;

locks the table fully, then

ALTER TABLE foo ADD COLUMN bar;
ALTER TABLE foo ENABLE TRIGGER USER;
COMMIT;

gets the job done. I only pause because I figured that the single DISABLE triggerin transaction would have flopped back
whenthe transaction committed. I was wrong about that.... I only need a little bit of affirmation or a kick in the
rightdirection. 

Thanks folks.

pgsql-general by date:

Previous
From: tv@fuzzy.cz
Date:
Subject: Re: simple update query too long
Next
From: Merlin Moncure
Date:
Subject: Re: stunnel with just postgresql client part