Re: Make mesage at end-of-recovery less scary.
От | Peter Eisentraut |
---|---|
Тема | Re: Make mesage at end-of-recovery less scary. |
Дата | |
Msg-id | 4a9fc5b1-34c8-46ec-9b71-d4763d70311d@2ndquadrant.com обсуждение исходный текст |
Ответ на | Re: Make mesage at end-of-recovery less scary. (Kyotaro Horiguchi <horikyota.ntt@gmail.com>) |
Ответы |
Re: Make mesage at end-of-recovery less scary.
Re: Make mesage at end-of-recovery less scary. |
Список | pgsql-hackers |
On 2020-03-05 08:06, Kyotaro Horiguchi wrote: > | [20866] LOG: replication terminated by primary server > | [20866] DETAIL: End of WAL reached on timeline 1 at 0/30001C8. > | [20866] FATAL: could not send end-of-streaming message to primary: no COPY in progress > | [20851] LOG: reached end of WAL at 0/30001C8 on timeline 1 in archive during standby mode > | [20851] DETAIL: invalid record length at 0/30001C8: wanted 24, got 0 > > I changed the above to the below, which looks more adequate. > > | [24271] LOG: replication terminated by primary server on timeline 1 at 0/3000240. > | [24271] FATAL: could not send end-of-streaming message to primary: no COPY in progress > | [24267] LOG: reached end of WAL at 0/3000240 on timeline 1 in archive during standby mode > | [24267] DETAIL: invalid record length at 0/3000240: wanted 24, got 0 Is this the before and after? That doesn't seem like a substantial improvement to me. You still get the "scary" message at the end. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: