Sadly not. I configured it manually. I did not use Slony in the end as one of its requirements is that every table should have a primary key. I did not have control over the database so in the end I just used the built in PostgreSQL replication.
On 27/08/2015 17:39, "snake77se" <snake7...@gmail.com> wrote: >Hello Aurelio, > >I have the same error, I saw that your messages are already several months >ago, I wanted to know if you found the solution to the error. > >Thanks in advance, > > > >-- >View this message in context: >http://postgresql.nabble.com/pgAdmin-III-v-1-20-0-and-Slony-I-v2-2-4-and-P >ostgresql-v9-4-4-tp5855985p5863608.html >Sent from the PostgreSQL - pgadmin support mailing list archive at >Nabble.com. > > >-- >Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) >To make changes to your subscription: >http://www.postgresql.org/mailpref/pgadmin-support > >______________________________________________________________________ >This email has been scanned by the Symantec Email Security.cloud service. >For more information please visit http://www.symanteccloud.com >______________________________________________________________________ ______________________________________________________________________ This email has been scanned by the Symantec Email Security.cloud service. For more information please visit http://www.symanteccloud.com ______________________________________________________________________ -- Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgadmin-support
