On Thu, May 27, 2010 at 9:49 PM, Iñigo Martinez Lasala <imartinez@xxxxxxxxxxxx> wrote: > Constraints are special triggers, but triggers anyway. > > So, If you truncate the table, create the contraint and then restore with > triggers disabled, it could be faster that create the contraint and wait > until it checks all table data... or not... :) > > > > -----Original Message----- > From: Nilesh Govindarajan <lists@xxxxxxxxxx> > To: Iñigo Martinez Lasala <imartinez@xxxxxxxxxxxx> > Cc: Amit jain <amitjain@xxxxxxxxxxxxx>, pgsql-admin@xxxxxxxxxxxxxx > Subject: Re: How to add constraints without validating data. > Date: Thu, 27 May 2010 21:45:25 +0530 > > How would disabling triggers help that ? He just wants to add > constraints without loss of data. I don't think he has any triggers. > > > I agree constraints are triggers. But as far as I know, truncating table doesn't disable the constraints. Its same as deleteing all rows and then altering the table. In that manner, even my solution would be appropriate because it creates a duplicate table with the constraints. Whatever be the method, I don't think its possible to avoid the constraints. Correct me if I'm wrong. -- Nilesh Govindarajan Facebook: nilesh.gr Twitter: nileshgr Website: www.itech7.com -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
