On Wed, Aug 21, 2013 at 5:09 AM, Fujii Masao wrote:
>> Thu Aug 15 18:33:09 MSK 2013 ERROR archive_wal.sh: Problem occured
>> during WAL archiving: pg_receivexlog: could not send feedback packet:
>> server closed the connection unexpectedly
>>
>> At the same time postgres reported this error in log
On Tue, Aug 20, 2013 at 3:17 PM, Sergey Konoplev wrote:
> Hi all,
>
> My WAL archiving script based on pg_receivexlog reported the following
> error several days ago (just ignore everything before
> 'pg_receivexlog', it's a message my script generates).
>
> Thu Aug 15 18:33:09 MSK 2013 ERROR archi
On Tue, Aug 20, 2013 at 2:10 AM, Magnus Hagander wrote:
> It looks like something outside postgres or pg_receivexlog did
> terminate the connection. pg_receievexlog noticed it was closed,
> whereas postgres waited for the timeout (but probably would've noticed
> if it had actually had some other d
On Tue, Aug 20, 2013 at 8:17 AM, Sergey Konoplev wrote:
> Hi all,
>
> My WAL archiving script based on pg_receivexlog reported the following
> error several days ago (just ignore everything before
> 'pg_receivexlog', it's a message my script generates).
>
> Thu Aug 15 18:33:09 MSK 2013 ERROR archi
Hi all,
My WAL archiving script based on pg_receivexlog reported the following
error several days ago (just ignore everything before
'pg_receivexlog', it's a message my script generates).
Thu Aug 15 18:33:09 MSK 2013 ERROR archive_wal.sh: Problem occured
during WAL archiving: pg_receivexlog: coul
