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
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?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

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