From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: RI triggers and schemas |
Date: | 2002-04-01 07:08:30 |
Message-ID: | 010301c1d94c$078122d0$0200a8c0@SOL |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Yeah, although it'd still be a good idea probably to convert the dump form
> to ALTER TABLE in any case. The one downside that was brought up in the
> past was the time involved in checking dumped (presumably correct) data
> when the constraint is added to very large tables. I can probably make
> that faster since right now it's just running the check on each row,
> but it'll still be slow on big tables possibly. Another option would
> be to have an argument that would disable the check on an add constraint,
> except that wouldn't work for unique/primary key.
Maybe it could be a really evil SET CONSTRAINTS command like:
SET CONSTRAINTS UNCHECKED;
...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2002-04-01 15:25:03 | Re: RI triggers and schemas |
Previous Message | Stephan Szabo | 2002-04-01 06:00:48 | Re: RI triggers and schemas |