From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Lukáš Sobotka <sobotka(dot)luk(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Foreign table & Connection reset by peer |
Date: | 2019-02-24 17:46:42 |
Message-ID: | 650cb78e-f9b4-2b87-ae80-e282bea0cb11@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/24/19 2:25 AM, Lukáš Sobotka wrote:
> Thanks for quick answer. I am feeling a little embarrassed that I did
> not find this before... The thread definitely helped me to understand more.
>
> When I execute query with foreign tables, the connection is created
> (according pg_stat_activity). The question is what I should do for
> ending the connection. I can get PID of connection and force to end it
Not sure. In the original thread the OP was calling conn.close() from
inside a Python script and still seeing the message. The only way they
could prevent it was to disable SSL. From what I gather this is down in
the internals of the code and needs a patch to fix. Someone with more
knowledge of this will need to comment further.
> by pg_terminate_backend, but that is not "clean way".
>
> Unfortunately I can not disable SSL encryption as it is mentioned in the
> thread. But it is interesting for me, that the log message (resetting by
> peer) is created only in encrypted connection, because in both way the
> connection stayed defined in pg_stat_activity after query on foreign table.
>
> so 23. 2. 2019 v 22:48 odesílatel Adrian Klaver
> <adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>> napsal:
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2019-02-24 18:38:51 | Re: Future Non-server Windows support??? |
Previous Message | Adrian Klaver | 2019-02-24 17:18:41 | Re: Future Non-server Windows support??? |