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

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 (view raw, whole thread or download thread mbox)
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
> > TABLE statement, and not as an ALTER TABLE statement after the data has
> > loaded.
> > Should we move it to after the data for speed purposes, like we have
> > 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?


In response to


pgsql-hackers by date

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

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