On Thu, Jan 21, 2010 at 12:45 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Jaime Casanova <jcasanov@systemguards.com.ec> writes:
>> When we perform a test migration of the data we found some errors on
>> the logs, one of them is this one:
>
>> """
>> mic=3D# ALTER TABLE tcom_invitacion ADD primary key (id_invitacion);
>> NOTICE: =C2=A0ALTER TABLE / ADD PRIMARY KEY will create implicit index
>> "tcom_invitacion_pkey" for table "tcom_invitacion"
>> ERROR: =C2=A0concurrent insert in progress
>> """
>
> Can you provide a reproducible test case?
>
trying to do so, gives me an error when moving the affected table from
the migration test database to my machine:
"""
ERROR: invalid byte sequence for encoding "UTF8": 0xed6261
HINT: This error can also happen if the byte sequence does not match
the encoding expected by the server, which is controlled by
"client_encoding".
CONTEXT: COPY tcom_invitacion, line 543881
"""
both servers had client_encoding and server_encoding in UTF8 and if i
try this from the real server i get no error, so i guess this was
somehow network corruption
i failed to say that i make the migration directly via the network:
$PG8.4DIR/bin/pg_dump -C -h ip_old_server dbname | $PG8.4DIR/bin/psql
--=20
Atentamente,
Jaime Casanova
Soporte y capacitaci=C3=B3n de PostgreSQL
Asesor=C3=ADa y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
