From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | Laura Castro <laura(at)alfa21(dot)com> |
Cc: | PostgresSQL ODBC mailing list <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Re: Indexes |
Date: | 2002-07-25 07:48:15 |
Message-ID: | 3D3FAD3F.289ED75E@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
Laura Castro wrote:
>
> I'm trying to perform a massive load on a postgreSQL database
> from ODBC, but I've found that if the table contains a 'PRIMARY
> KEY' constraint, the sql-insert sentences from my program fail.
> I've also noticed that after creating the table, the ODBC driver
> (unixODBC) warnings me this way:
>
> NOTICE: CREATE TABLE/PRIMARY KEY will create implicit index for table
>
> so I think if I could `deactivate' the index before doing the massive
> load it could possibly work, but I can't find the way of deactivating
> indexes looking at the documentation. Can this be done?
Unfortunately no.
> If not, any idea
> about another suitable solution?
You can drop the index before doing the massive load and
can create a unique index with the same name after it.
The only difference is that pg_index.inidisprimary is
set to true or not.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
From | Date | Subject | |
---|---|---|---|
Next Message | Hiroshi Inoue | 2002-07-25 08:29:25 | Re: Write Conflict |
Previous Message | Moez Hielmy | 2002-07-25 02:10:30 | Write Conflict |