From: Shane Ambler <pgsql@Sheeky.Biz>
To: Bill Moran <wmoran@collaborativefusion.com>
Cc: henk de wit <henk53602@hotmail.com>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date: Thu, 28 Aug 2008 02:15:52 +0930
Message-ID: <48B584C0.6080204@Sheeky.Biz> (raw)
In-Reply-To: <20080827090123.c0e8e638.wmoran@collaborativefusion.com>
References: <BAY124-W57D3654AF1159CAF8EAC19F5660@phx.gbl>
<dcc563d10808261123q57c8797bk77bc00eb949fc747@mail.gmail.com>
<BAY124-W383ADB13D25B83F8B60E92F5660@phx.gbl>
<20080827090123.c0e8e638.wmoran@collaborativefusion.com>
Bill Moran wrote:
> On a side note, what version of PG are you using? If it was in a
> previous email, I missed it.
>
He mentioned 8.3.1 in the first email.
Although nothing stands out in the 8.3.2 or 8.3.3 fix list (without
knowing his table structure or any contrib modules used) I wonder if
one of them may resolve his issue.
I also wonder if the error is actually sent back from postgresql or
whether jdbc is throwing the exception because of a timeout waiting for
a response. I would think that with the table in use having 22GB data
and 13GB indexes that the long running query has a chance of creating a
delay on the connections that is long enough to give jdbc the impression
that it isn't responding - generating a misleading error code of "An I/O
error" (meaning we know the server got the request but the response from
the server isn't coming back)
Can you increase the timeout settings on the insert connections that are
failing?
--
Shane Ambler
pgSQL (at) Sheeky (dot) Biz
Get Sheeky @ http://Sheeky.Biz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: pgsql@Sheeky.Biz, wmoran@collaborativefusion.com, henk53602@hotmail.com
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
In-Reply-To: <48B584C0.6080204@Sheeky.Biz>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox