From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matthias Apitz <guru(at)unixarea(dot)de> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;' |
Date: | 2020-04-27 13:58:54 |
Message-ID: | 17437.1587995934@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Matthias Apitz <guru(at)unixarea(dot)de> writes:
> As the client seems to be waiting on the server and the server on the
> client... could it have been caused by this in /etc/hosts (what our IT
> department configured):
Doubt it. Your connection evidently got through (at least) the
authentication exchange, so basic data transmission seems to be
working. I speculate that there's something data-dependent about
the command that's failing.
As an example, it would not be terribly surprising to get a behavior
like this if there were something deciding to do an LF -> CRLF or
similar transformation on the data stream. The substitution might
accidentally not trigger during authentication, only to break some
actual query a bit later. But there really shouldn't be anything
making such changes in our data stream.
Still, looking at recent network-level configuration changes wouldn't
be a bad idea.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Mahendra Singh Thalor | 2020-04-27 14:27:26 | Re: How to debug "background worker "parallel worker" (PID 32152) was terminated by signal 11: Segmentation fault" |
Previous Message | Tom Lane | 2020-04-27 13:40:39 | Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;' |