Re: postgres 9.3 postgres_fdw ::LOG: could not receive data from client: Connection reset by peer

From: Vladimir Svedov <vodevsh(at)gmail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: postgres 9.3 postgres_fdw ::LOG: could not receive data from client: Connection reset by peer
Date: 2016-11-24 13:12:23
Message-ID: CADqDLE_pyjn9YS4NNyPAA5CKOrHVBOL6zwWuY9=MVmiu9jYSbg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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(at)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

2016-11-23 18:16 GMT+00:00 Jeff Janes <jeff(dot)janes(at)gmail(dot)com>:

> On Mon, Nov 21, 2016 at 6:32 AM, Vladimir Svedov <vodevsh(at)gmail(dot)com>
> wrote:
>
>> Hi,
>> I have this question. Looked for a help on http://dba.stackexchange.com/
>> No success.
>> Maybe you can answer?..
>> Thank you in advance
>>
>>
>> "FOREIGN_TABLE" created with postgres_fdw. LOCAL_TABLE is just a local
>> table...
>>
>> Symptoms:
>>
>> 1. I run in psql query SELECT * from FOREIGN_TABLE. No log generated
>> 2. I run in bash psql -c "SELECT * from LOCAL_TABLE". No log generated
>> 3. I run in bash psql -c "SELECT * from FOREIGN_TABLE". ::LOG: could
>> not receive data from client: Connection reset by peer generated in
>> postgres log
>>
>>
> Which server log file is this generated in, the local or the foreign?
> Whichever it is, is there an entry in the logfile for the other server
> which seems to match up to this one? That may have more useful details.
>
> Cheers,
>
> Jeff
>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2016-11-24 13:30:57 Re: [bugfix] commit timestamps ERROR on lookup of FrozenTransactionId
Previous Message Karl O. Pinc 2016-11-24 13:01:46 Re: Patch to implement pg_current_logfile() function