On 6/8/17 01:57, Noah Misch wrote: > On Fri, Jun 02, 2017 at 11:51:26AM -0700, Andres Freund wrote: >> commit 7c4f52409a8c7d85ed169bbbc1f6092274d03920 >> Author: Peter Eisentraut <pete...@gmx.net> >> Date: 2017-03-23 08:36:36 -0400 >> >> Logical replication support for initial data copy >> >> made walreceiver emit worse messages in v10 than before when the master >> gets shut down. Before 10 you'll get something like: >> >> 2017-06-02 11:46:07.173 PDT [16143][] LOG: replication terminated by >> primary server >> 2017-06-02 11:46:07.173 PDT [16143][] DETAIL: End of WAL reached on >> timeline 1 at 0/1B7FB8C8. >> 2017-06-02 11:46:07.173 PDT [16143][] FATAL: could not send >> end-of-streaming message to primary: no COPY in progress >> >> the last bit is a bit superflous, but it still kinda makes sense. Now >> you get: >> 2017-06-02 11:47:09.362 PDT [17061][] FATAL: unexpected result after >> CommandComplete: server closed the connection unexpectedly >> This probably means the server terminated abnormally >> before or while processing the request. > > [Action required within three days. This is a generic notification.]
This was fixed by Andres. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
