Hi Adrian, thank you very much for your response.
I ran the "VACUUM ANALYZE" command on the master node. Regarding log messages. Here is the contents of the log (excluding connections/disconnections): 2016-02-22 02:30:08 GMT 24616 LOG: recovery has paused 2016-02-22 02:30:08 GMT 24616 HINT: Execute pg_xlog_replay_resume() to continue. 2016-02-22 02:37:19 GMT 23859 DBNAME ERROR: missing chunk number 0 for toast value 2747579 in pg_toast_22066 2016-02-22 02:37:19 GMT 23859 DBNAME STATEMENT: COPY public.room_shape (room_uuid, data) TO stdout; 2016-02-22 02:37:41 GMT 2648 DBNAME LOG: could not receive data from client: Connection reset by peer 2016-02-22 02:37:41 GMT 2648 DBNAME LOG: unexpected EOF on client connection Best regards, Fredrik Huitfeldt On 7 March 2016 16:35:29 +01:00, Adrian Klaver <adrian.kla...@aklaver.com> wrote: > On 03/06/2016 10:18 PM, <fred...@huitfeldt.com> wrote: > > > HI All, > > > > i would really appreciate any help I can get on this issue. > > > > basically, a pg_basebackup + streaming attach, led to a database that we > > could not read from afterwards. > > > From original post: > > <http://www.postgresql.org/message-id/1456919678340.31300.116900@webmail2> > > "The issue remained until we ran a full vacuum analyze on the cluster." > > Which cluster was that, the master or the slave? > > "I have logfiles from the incident, but I cannot see anything out of the > ordinary (despite having a fair amount of experience investigating postgresql > logs)." > > > Can we see the section before and after ERROR? > > > > > > Beset regards, > > Fredrik > > > > PS please advise if this is better posted on another list. > > > > -- > Adrian Klaver > <adrian.kla...@aklaver.com> >
