Re: record with incorrect prev-link
От | Bernd Helmle |
---|---|
Тема | Re: record with incorrect prev-link |
Дата | |
Msg-id | 9758CFA9378D0C798E10C32D@amenophis обсуждение исходный текст |
Ответ на | record with incorrect prev-link (Philippe Rimbault <primbault@edd.fr>) |
Ответы |
Re: record with incorrect prev-link
|
Список | pgsql-testers |
--On 14. September 2010 11:42:45 +0200 Philippe Rimbault <primbault@edd.fr> wrote: > I've found this message in my server log (on the standby server) : > ... > 2010-09-14 11:10:51 CEST ( )LOG: record with incorrect prev-link > 1/798BDFC4 at 1/7B8BE010 > 2010-09-14 11:10:51 CEST ( )FATAL: terminating walreceiver process due > to administrator command > cp: impossible d'évaluer « /opt/wal/00000001000000010000007B »: Aucun > fichier ou dossier de ce type > 2010-09-14 11:10:51 CEST ( )LOG: record with incorrect prev-link > 1/798BDFC4 at 1/7B8BE010 > cp: impossible d'évaluer « /opt/wal/00000001000000010000007B »: Aucun > fichier ou dossier de ce type > 2010-09-14 11:10:51 CEST ( )LOG: streaming replication successfully > connected to primary > ... > (i'm french, the message "Aucun fichier ou dossier de ce type" = "no such > file or directory") Maybe i'm wrong, but if I understand the code correctly this could mean that the walreceiver got a corrupted wal record, was shut down and the retry code retried recovering from the archive. Just guessing, but maybe there are issues with your network connectivity involved? Are you keeping getting such errors? -- Thanks Bernd
В списке pgsql-testers по дате отправления: