Local server log has the line and remote table log is empty (it is configured for minimum warning and when I produce one it appears in log OK)
And I have new details - it happens on some additional environments - not constantly. Some hours it happens every time, then just stops appearing:
postgres@hostname:~$ grep user 9.3/main/pg_log/postgresql-2016-11-22_000000.log | cat -n
1 2016-11-22 06:00:02 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
2 2016-11-22 06:00:03 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
3 2016-11-22 06:00:03 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
4 2016-11-22 10:06:08 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
5 2016-11-22 10:06:08 UTC 127.0.0.1 user ::LOG: could not receive data from client: Connection reset by peer
6 2016-11-22 10:06:08 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
7 2016-11-22 11:25:27 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
8 2016-11-22 11:25:27 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
9 2016-11-22 11:25:27 UTC 127.0.0.1 user::LOG: could not receive data from client: Connection reset by peer
this is log from local server where user runs same bunch of three statements MINUTELY
But when it start happening if I psql to db, same statement produces NOT this string in log.
Here reason why you should not follow this post any more:
postgres=# select version();
version
----------------------------------------------------------------------------------------------
PostgreSQL 9.3.9 on x86_64-unknown-linux-gnu, compiled by gcc (Debian 4.7.2-5) 4.7.2, 64-bit
(1 row)
I will just upgrade it. And this is the only machine I have this weird behavior at.
Sorry guys and thank you for your time