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

Re: CHECK constraints in pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
Cc: "Hackers" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: CHECK constraints in pg_dump
Date: 2003-02-26 06:56:48
Message-ID: 27689.1046242608@sss.pgh.pa.us (view raw or flat)
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?

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Dave CramerDate: 2003-02-26 07:19:25
Subject: Re: autocommit off mode, how does it work?
Previous:From: Christopher Kings-LynneDate: 2003-02-26 06:47:33
Subject: CHECK constraints in pg_dump

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