Re: CHECK constraints in pg_dump

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CHECK constraints in pg_dump
Date: 2003-02-26 07:53:52
Message-ID: 019801c2dd6c$3491c4d0$6500a8c0@fhp.internal
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> writes:
> > I notice that we're still dumping CHECK constraints as part of the
CREATE
> > TABLE statement, and not as an ALTER TABLE statement after the data has
been
> > loaded.
>
> > Should we move it to after the data for speed purposes, like we have
with
> > all other constraints?
>
> Why would there be any speed advantage?

Is it not faster to add it when all the data is there, rather than
evaluating it as each row is inserted, like indexes?

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antti Haapala 2003-02-26 08:56:21 Re: How do I change the server encoding?
Previous Message Rajesh Kumar Mallah 2003-02-26 07:29:23 Re: Index File growing big.