From: | Laura Castro <laura(at)alfa21(dot)com> |
---|---|
To: | PostgresSQL ODBC mailing list <pgsql-odbc(at)postgresql(dot)org> |
Subject: | Indexes |
Date: | 2002-07-24 09:44:27 |
Message-ID: | Pine.LNX.4.44.0207241136250.25330-100000@dugtrio.alfa21.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
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? If not, any idea
about another suitable solution?
Creating the PRIMARY KEY constraint after the massive load won't work,
because postgreSQL 7.1.3 doesn't implement the ALTER TABLE ... ADD
CONSTRAINT sentence with this kind of constraint.
Thank you very much in advance.
Laura Castro
From | Date | Subject | |
---|---|---|---|
Next Message | Janet Borschowa | 2002-07-25 00:31:43 | Specifying Max LongVarChar in odbcinst.ini doesn't work |
Previous Message | Laura Castro | 2002-07-23 16:32:33 | COPY alternative? |