From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | ZhongMing C <czmy(at)hotmail(dot)com> |
Cc: | "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
Subject: | Re: BUG #15054: intermittent error: An I/O error occured while sending to the backend. |
Date: | 2018-02-07 19:24:06 |
Message-ID: | CAKFQuwa5z_cuLDD8cdqxJBH7HUVsHppvohXnXHDvincpiNb96g@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Wed, Feb 7, 2018 at 12:12 PM, ZhongMing C <czmy(at)hotmail(dot)com> wrote:
> Hi,
>
> Our JDBC driver version is kind of outdated (9.1). But upgrading to 42.2.1
> makes no difference. Still failed with around the same rate.
>
> Restarting the DB client or DB server makes no difference.
>
> We only have one DB client app connecting to the database. Therefore, we
> can't tell whether this is a general problem or not.
>
> Could you advise how I could do to collect the server log which can
> contain most of the information you need to troubleshoot?
>
The convention on these lists is to bottom or inline post - not top-post.
The default log location is probably specific to RHEL (I use Ubuntu) but
usually it is found in either the data directory or a system location
probably under /var/log
Dave
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2018-02-08 00:34:18 | Re: BUG #15036: Un-killable queries Hanging in BgWorkerShutdown |
Previous Message | ZhongMing C | 2018-02-07 19:12:58 | Re: BUG #15054: intermittent error: An I/O error occured while sending to the backend. |