| From: | Bruno Wolff III <bruno(at)wolff(dot)to> |
|---|---|
| To: | Mark Lewis <mark(dot)lewis(at)mir3(dot)com> |
| Cc: | Merlin Moncure <mmoncure(at)gmail(dot)com>, Scott Marlowe <smarlowe(at)g2switchworks(dot)com>, Karen Hill <karen_hill22(at)yahoo(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: How long should it take to insert 200,000 records? |
| Date: | 2007-02-06 18:37:52 |
| Message-ID: | 20070206183752.GB22967@wolff.to |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Tue, Feb 06, 2007 at 10:31:26 -0800,
Mark Lewis <mark(dot)lewis(at)mir3(dot)com> wrote:
>
> Sure it's possible:
>
> CREATE TABLE parent (col1 int4);
> -- insert many millions of rows into parent
> CREATE TABLE child (col1 int4 REFERENCES parent(col1));
> -- insert many millions of rows into child, very very slowly.
I don't think Postgres allows this. You don't have to have an index in the
child table, but do in the parent table.
Quote from http://developer.postgresql.org/pgdocs/postgres/sql-createtable.html:
The referenced columns must be the columns of a unique or primary key
constraint in the referenced table.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2007-02-06 19:06:32 | Re: How long should it take to insert 200,000 records? |
| Previous Message | Mark Lewis | 2007-02-06 18:31:26 | Re: How long should it take to insert 200,000 records? |