Postgresql - Principal listen_addresses = '*' wal_level = hot_standby max_wal_senders = 1 wal_keep_segments = 40
Postgresql - Secundário hot_standby=on Recovery - Secundário standby_mode = on primary_conninfo = 'host=ip_number port=port_number user=user password=pass' trigger_file = '/path/failover.trg' Em 11 de janeiro de 2012 17:00, Leonardo Cezar <lhce...@gmail.com> escreveu: > 2012/1/11 Dauro Sobrinho <dauroadpostg...@gmail.com>: > > Ao tentar subir a replicação o seguinte log é gerado: > > > > LOG: database system was interrupted while in recovery at log time > > 2012-01-11 16:48:31 BRST > > HINT: If this has occurred more than once some data might be corrupted > and > > you might need to choose an earlier recovery target. > > [corte] > > > Mas no postgresql.conf do servidor principal o wal_level está setado como > > hot_standby, gostaria de saber se alguém já se deparou com esse problema > e > > se tem a solução? > > Descreva as configurações de ambos servidores (postgres.conf). > > -Leo > -- > Leonardo Cezar > http://postgreslogia.wordpress.com > _______________________________________________ > pgbr-geral mailing list > pgbr-geral@listas.postgresql.org.br > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral > -- Att, Dauro Lima Sobrinho *DBA PostgreSQL* * DB2 Database Administrator for LUW - IBM Information Management DB2 Certified Database Associate - IBM Information Management DB2 Technical Mastery v2 - IBM Information Management Informix Dynamic Server - IBM Information Management SQL Server 2008 - Microsoft Certified Technology Specialist *
_______________________________________________ pgbr-geral mailing list pgbr-geral@listas.postgresql.org.br https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
