<div dir="ltr"><div><div>As you told, table seemed to be corrupted. I got two rows from this select:<br>SELECT bco_cod, pla_cod, COUNT(*) from "8357_isarq"."wm_bco_pla" GROUP BY bco_cod, pla_cod HAVING COUNT(*) > 1; <br><br></div>Ran a delete to remove the two rows and SLONY could continue on with the processing.<br><br></div><div>Hope to get the replication finished soon in order to end the migration from 8.3 to 9.3.<br></div><div><br></div>Thank you!<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Dec 16, 2014 at 12:16 PM, Andrew Sullivan <span dir="ltr"><<a href="mailto:ajs@crankycanuck.ca" target="_blank">ajs@crankycanuck.ca</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Tue, Dec 16, 2014 at 08:32:03AM -0200, Carlos Henrique Reimer wrote:<br>
> Hi,<br>
><br>
> I'm trying to replicate a postgresql database 8.3 with 1TB data and about<br>
<br>
</span>8.3.what? And also, is that a typo, or do you really mean 8.3? If<br>
so, I hope you're aware that you're running a database system that was<br>
EOL'd by the community almost two years ago.<br>
<br>
On the issue:<br>
<span class=""><br>
> "8357_isarq"."wm_bco_pla"; " PGRES_FATAL_ERROR ERROR: could not create<br>
> unique index "pk_wm_bco_pla"<br>
> DETAIL: Key (bco_cod, pla_cod)=(399, 5056110) is duplicated.<br>
> CONTEXT: SQL statement "reindex table "8357_isarq"."wm_bco_pla""<br>
<br>
</span><span class="">> The error indicates "8357_isarq"."wm_bco_pla" has duplicated rows for<br>
> primary key (bco_cod, pla_cod)=(399, 5056110) but when I query the table<br>
> using this pk I got only one row:<br>
><br>
> select * from "8357_isarq"."wm_bco_pla" where bco_cod=399 and pla_cod =<br>
> '5056110';<br>
> bco_cod | pla_cod | pla_des | ativo |<br>
> conta_pai | pla_itlistserv | pla_ctacosif<br>
> ---------+---------+---------------------------------------+-------+-----------+----------------+--------------<br>
> 399 | 5056110 | RENDAS TRANSACOES VISA ELETRON - HBBR | S |<br>
> 5056004 | 1501 | 71799003<br>
> (1 row)<br>
<br>
</span>Are you quite sure that your source table isn't corrupt? That'd be my<br>
first suspicion. I'd dump the source table and look for a duplicate<br>
before jumping to the conclusion that you are going to "lose three<br>
days of replication processing". Your replica may in fact contain a<br>
copy of a corrupted database, and it might be tripping on this.<br>
<br>
Best regards,<br>
<br>
A<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Andrew Sullivan<br>
<a href="mailto:ajs@crankycanuck.ca">ajs@crankycanuck.ca</a><br>
_______________________________________________<br>
Slony1-general mailing list<br>
<a href="mailto:Slony1-general@lists.slony.info">Slony1-general@lists.slony.info</a><br>
<a href="http://lists.slony.info/mailman/listinfo/slony1-general" target="_blank">http://lists.slony.info/mailman/listinfo/slony1-general</a><br>
</font></span></blockquote></div><br clear="all"><br>-- <br><div class="gmail_signature">Reimer<br>47-3347-1724 47-9183-0547 msn: <a href="mailto:carlos.reimer@opendb.com.br">carlos.reimer@opendb.com.br</a><br></div>
</div>