Debugging I/O errors occured while reading from backend

From: Peter Royal <proyal(at)pace2020(dot)com>
To: pgsql-jdbc(at)postgresql(dot)org
Subject: Debugging I/O errors occured while reading from backend
Date: 2003-08-15 15:13:28
Message-ID: 062A93F6-CF33-11D7-A863-000393B61B56@pace2020.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

(Didn't seem to go through the first time..)

I'm getting exceptions about "An I/O error occured while reading from
backend" occuring under load.

From reading in the archives,
<http://archives.postgresql.org/pgsql-jdbc/2001-04/msg00050.php> and
<http://archives.postgresql.org/pgsql-general/2001-07/msg01271.php> the
primary suggestion is to enable postmaster logging.

I had enabled log_connections, but that didn't show anything.

I'm asking rather than just dialing up the log verbosity because this
is occurring in a production environment and I didn't want to slow them
down with overly verbose logging.

Any help is appreciated. Thanks!!
-peter

Below are my settings from postgresql.conf:

Things i changed:

syslog = 2
syslog_facility = 'LOCAL5'

Defaults:

#
# Message display
#
#server_min_messages = notice # Values, in order of decreasing detail:
# debug5, debug4, debug3, debug2,
debug1,
# info, notice, warning, error, log,
fatal,
# panic
#client_min_messages = notice # Values, in order of decreasing detail:
# debug5, debug4, debug3, debug2,
debug1,
# log, info, notice, warning, error
#silent_mode = false

#log_connections = false
#log_pid = false
#log_statement = false
#log_duration = false
#log_timestamp = false

#log_min_error_statement = error # Values in order of increasing
severity:
# debug5, debug4, debug3, debug2,
debug1,
# info, notice, warning, error,
panic(off)

Browse pgsql-jdbc by date

  From Date Subject
Next Message Paul Thomas 2003-08-15 15:22:17 Re: CVS JDBC driver will try to use server-side-prepare on unpreparable SQL
Previous Message kevin 2003-08-15 14:12:09 resultset.first() untrappable error