From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | add primary key doesn't block? |
Date: | 2010-01-21 17:38:56 |
Message-ID: | 3073cc9b1001210938x5df093c8o10b3ec3057be4ae2@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
I'm testing the migration procedure for a client, we want to migrate
from 8.3.6 to 8.4
When we perform a test migration of the data we found some errors on
the logs, one of them is this one:
"""
mic=# ALTER TABLE tcom_invitacion ADD primary key (id_invitacion);
NOTICE: ALTER TABLE / ADD PRIMARY KEY will create implicit index
"tcom_invitacion_pkey" for table "tcom_invitacion"
ERROR: concurrent insert in progress
"""
actually, no indexes were created on this table...
and when i tried to add the PK manually after migration i get this
same error (not always, it seems this time the index is being created
but this time i did it inside a transaction)...
doesn't the index creation of the index block the table so, that
message should not appear?
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-01-21 17:45:14 | Re: add primary key doesn't block? |
Previous Message | Milen A. Radev | 2010-01-21 17:17:39 | Re: BUG #5290: Simple loop with insert into and check to avoid duplicate values fails |