Opa, 2012/7/12 Antonio Abner Junior <[email protected]>
> Srs, > > Eu ja fiz essa implementação algumas vezes mas agora não sei o que está > acontecendo que está apresentando erro. > Utilizo o pgbasebackup e após ele finalizar faço as devidas alterações e > ao iniciar ocorre o erro > Quando faço a moda antiga funciona ! Alguém ja executou isso dessa forma ? > Qual o procedimento completo que você fez? > > > MASTER > POSTGRESQL.CONF > > #------------------------------------------------------------------------------ > # WRITE AHEAD LOG > > #------------------------------------------------------------------------------ > # - Settings - > wal_level = hot_standby # minimal, archive, or hot_standby > # (change requires restart) > synchronous_commit = on # synchronization level; on, off, or local > # - Archiving - > archive_mode = on # allows archiving to be done > # (change requires restart) > archive_command = 'cp -i %p /wal/archive/%f' # command to use > to archive a logfile segment > > > #------------------------------------------------------------------------------ > # REPLICATION > > #------------------------------------------------------------------------------ > # - Master Server - > # These settings are ignored on a standby server > max_wal_senders = 15 # max number of walsender processes > # (change requires restart) > synchronous_standby_names = 'XX.X.XX.XXX' # standby servers that > provide sync rep > # comma-separated list of application_name > # from standby(s); '*' = all > > SLAVE > POSTGRESQL.CONF > > #------------------------------------------------------------------------------ > # WRITE AHEAD LOG > > #------------------------------------------------------------------------------ > # - Settings - > synchronous_commit = on # synchronization level; on, off, or local > > > #------------------------------------------------------------------------------ > # REPLICATION > > #------------------------------------------------------------------------------ > > # - Standby Servers - > # These settings are ignored on a master server > hot_standby = on # "on" allows queries during > recovery > # (change requires restart) > > > RECOVERY.CONF > standby_mode = 'true' > primary_conninfo = 'host=xx.x.xx.xx port=xxxx user=user1 > application_name=xx.x.xx.xx' > trigger_file = '/tmp/arquivo_gatilho.pgsql' > > > -bash-4.1$ pg_basebackup -U postgres -h xx.x.xx.xx -D /data/9.1 > could not identify current directory: Arquivo ou diretório não encontrado > NOTICE: pg_stop_backup complete, all required WAL segments have been > archived > -bash-4.1$ cd /data/9.1/ > -bash-4.1$ pg_ctl start -D /data/9.1/ > servidor está iniciando > log error: > LOG: database system was interrupted; last known up at 2012-07-12 > 08:03:39 BRT > LOG: creating missing WAL directory "pg_xlog/archive_status" > LOG: entering standby mode > LOG: trigger file found: /tmp/arquivo_gatilho.pgsql > LOG: invalid checkpoint record > FATAL: could not locate required checkpoint record > HINT: If you are not restoring from a backup, try removing the file > "/data/9.1/backup_label". > LOG: startup process (PID 6817) exited with exit code 1 > LOG: aborting startup due to startup process failure > LOG: database system was interrupted; last known up at 2012-07-12 > 08:03:39 BRT > LOG: entering standby mode > LOG: trigger file found: /tmp/arquivo_gatilho.pgsql > LOG: invalid checkpoint record > FATAL: could not locate required checkpoint record > HINT: If you are not restoring from a backup, try removing the file > "/data/9.1/backup_label". > LOG: startup process (PID 6864) exited with exit code 1 > LOG: aborting startup due to startup process failure > > > Antonio Abner Junior - AJ > > _______________________________________________ > pgbr-geral mailing list > [email protected] > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral > > Abraços -- JotaComm http://jotacomm.wordpress.com
_______________________________________________ pgbr-geral mailing list [email protected] https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
