ok foi bem isso mesmo Flávio, o Euler já tinha comentado também... foi só deletar ...postmaster.pid q ele subiu certinho....tava batendo cabeça... então não preciso deletar os dados do pg_xlog na restauração ? é isso mesmo...? os erros no arquivo de saída podem ser por esse motivo?
valeu.... log de saída: LOG: database system was interrupted; last known up at 2011-09-26 13:05:41 BRT LOG: starting archive recovery LOG: restored log file "000000010000000000000004" from archive LOG: redo starts at 0/4000020 LOG: consistent recovery state reached at 0/5000000 LOG: restored log file "000000010000000000000005" from archive LOG: restored log file "000000010000000000000006" from archive LOG: restored log file "000000010000000000000007" from archive LOG: restored log file "000000010000000000000008" from archive LOG: restored log file "000000010000000000000009" from archive LOG: restored log file "00000001000000000000000A" from archive LOG: restored log file "00000001000000000000000B" from archive LOG: restored log file "00000001000000000000000C" from archive LOG: restored log file "00000001000000000000000D" from archive LOG: restored log file "00000001000000000000000E" from archive LOG: restored log file "00000001000000000000000F" from archive LOG: restored log file "000000010000000000000010" from archive LOG: restored log file "000000010000000000000011" from archive LOG: restored log file "000000010000000000000012" from archive LOG: restored log file "000000010000000000000013" from archive LOG: restored log file "000000010000000000000014" from archive FATAL: the database system is starting up LOG: restored log file "000000010000000000000015" from archive LOG: restored log file "000000010000000000000016" from archive LOG: restored log file "000000010000000000000017" from archive LOG: restored log file "000000010000000000000018" from archive LOG: restored log file "000000010000000000000019" from archive LOG: restored log file "00000001000000000000001A" from archive cp: impossÃvel fazer stat em `/home/postgres/replicacao/archive/00000001000000000000001B': Arquivo ou diretório não encontrado LOG: could not open file "pg_xlog/00000001000000000000001B" (log file 0, segment 27): Arquivo ou diretório não encontrado LOG: redo done at 0/1A8FC758 LOG: last completed transaction was at log time 2011-09-26 14:15:46.591136-03 LOG: restored log file "00000001000000000000001A" from archive cp: impossÃvel fazer stat em `/home/postgres/replicacao/archive/00000002.history': Arquivo ou diretório não encontrado LOG: selected new timeline ID: 2 cp: impossÃvel fazer stat em `/home/postgres/replicacao/archive/00000001.history': Arquivo ou diretório não encontrado Em 27 de setembro de 2011 11:27, Flavio Henrique Araque Gurgel < [email protected]> escreveu: > >> pg_ctl: another server might be running; trying to start server anyway > >> pg_ctl: could not start server > >> Examine the log output. > > > > Removeu o postmaster.pid? > > Apenas complementando, na versão 9.0 (acho que desde a 8.3) se esse > arquivo existir, o PostgreSQL tenta subir o servidor mesmo assim, > atualizando esse arquivo, daí a string "trying to start server > anyway". > > Vi dois erros aí no Hélio. O das permissões vocês já mataram. > O outro, é que *não* precisa copiar os logs de transação arquivados > para o $PGDATA/pg_xlog a ser refeito. > Quem faz isso é o restore_command, automaticamente. > > > []s > Flavio Gurgel > _______________________________________________ > pgbr-geral mailing list > [email protected] > https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral > -- -- Hélio José (61) 99840139
_______________________________________________ pgbr-geral mailing list [email protected] https://listas.postgresql.org.br/cgi-bin/mailman/listinfo/pgbr-geral
