Well, for now it´s solved but I´ll explain what happens to solve it better on future. Suppose on Master you have a database with hundreds of schemas with same structure, so table Customer happens 500 times on that DB. That database being replicated with publication/subscription for all tables model, just that. Now to have new schemas added to this database you go to replica, create them with structure only, go to master and create them with data, go back to replica and refresh publication. But then imagine that one of those schemas you´ve created on replica with data. This is where problem occurs and message is just PK of Table Customer is duplicated but is not easy to find which table because I´ll have that table and that key on 90% of my schemas. If, on error message we just have which schema belongs that table would be great. -- Sent from: https://www.postgresql-archive.org/PostgreSQL-general-f1843780.html
