Albrecht =?iso-8859-1?b?RHJl3w==?= writes:
> A different, confusing point (which is closer to a “bug” IMHO) is that
> connections to localhost are actually encrypted by default. This is
> basically useless and just a waste of cpu cycles – if a malicious user may
> somehow tap (tcpdump) lo, the
Hi Tom:
Am 22.03.18 23:55 schrieb(en) Tom Lane:
It finally occurred to me what is a likely explanation for why you're seeing
these messages but I don't when I test postgres_fdw locally: probably, you are
encrypting connections to the foreign server with SSL.
I can confirm that the confusing
Michael Paquier writes:
> On Thu, Mar 22, 2018 at 06:55:12PM -0400, Tom Lane wrote:
>> Anyway, it's clearly not very nice that postgres_fdw makes no attempt
>> to do a graceful shutdown of its remote connection. I don't know that
>> this rises to the level of a bug, exactly, but if somebody wante
On Thu, Mar 22, 2018 at 06:55:12PM -0400, Tom Lane wrote:
> Anyway, it's clearly not very nice that postgres_fdw makes no attempt
> to do a graceful shutdown of its remote connection. I don't know that
> this rises to the level of a bug, exactly, but if somebody wanted to
> send in a patch it'd pr
Albrecht =?iso-8859-1?b?RHJl3w==?= writes:
> No messages are printed whilst the session is open. However, when I quit the
> session by typing “\q” /after/ entering the command above, the LOG message
> appears. It does not appear when I query tables from my_db exclusively,
> though, i.e. when
On 03/22/2018 11:08 AM, Albrecht Dreß wrote:
Hi Adrian:
Am 21.03.18 19:25 schrieb(en) Adrian Klaver:
Does it also happen when you open a psql session and do?:
psql>select * from ext_table limit 1;
No messages are printed whilst the session is open. However, when I
quit the session by typin
Hi Adrian:
Am 21.03.18 19:25 schrieb(en) Adrian Klaver:
Does it also happen when you open a psql session and do?:
psql>select * from ext_table limit 1;
No messages are printed whilst the session is open. However, when I quit the
session by typing “\q” /after/ entering the command above, the
On 03/21/2018 11:15 AM, Albrecht Dreß wrote:
Hi Adrian & Tom:
Thanks a lot for your input!
Am 20.03.18 20:38 schrieb(en) Tom Lane:
See comments inline below.
Unfortunately, in my original post, I confused the primary and secondary
(accessed via the FDW) data bases in my example when I anon
Hi Adrian & Tom:
Thanks a lot for your input!
Am 20.03.18 20:38 schrieb(en) Tom Lane:
My suspicion is it has to do with this:
postgres_fdw establishes a connection to a foreign server during the first
query that uses a foreign table associated with the foreign server. This
connection is kept
Adrian Klaver writes:
> On 03/20/2018 11:52 AM, Albrecht Dreß wrote:
>> I use Postgres 10.3 on a Debian Stretch system with foreign tables, and
>> noticed strange LOG messages when accessing them.
>> [time stamp/pid] user@my_db LOG: could not receive data from client:
>> Connection reset by pee
On 03/20/2018 11:52 AM, Albrecht Dreß wrote:
Hi all,
I use Postgres 10.3 on a Debian Stretch system with foreign tables, and
noticed strange LOG messages when accessing them.
The data base setup is basically
---8<---
Hi all,
I use Postgres 10.3 on a Debian Stretch system with foreign tables, and noticed
strange LOG messages when accessing them.
The data base setup is basically
---8<--
CREATE EXTENSION IF NOT EXISTS post
12 matches
Mail list logo
