From: Greg Smith <gsmith@gregsmith.com>
To: Scott Marlowe <scott.marlowe@gmail.com>
Cc: henk de wit <henk53602@hotmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: select on 22 GB table causes "An I/O error occured while sending to the backend." exception
Date: Fri, 29 Aug 2008 00:31:23 -0400 (EDT)
Message-ID: <Pine.GSO.4.64.0808290020060.23621@westnet.com> (raw)
In-Reply-To: <dcc563d10808261123q57c8797bk77bc00eb949fc747@mail.gmail.com>
References: <BAY124-W57D3654AF1159CAF8EAC19F5660@phx.gbl>
<dcc563d10808261123q57c8797bk77bc00eb949fc747@mail.gmail.com>
On Tue, 26 Aug 2008, Scott Marlowe wrote:
> If it is a checkpoint issue then you need more aggresive bgwriter
> settings, and possibly more bandwidth on your storage array.
Since this is 8.3.1 the main useful thing to do is increase
checkpoint_segments and checkpoint_completion_target to spread the I/O
over a longer period. Making the background writer more aggressive
doesn't really help with
What is checkpoint_segments set to on this system? If it's still at the
default of 3, you should increase that dramatically.
> What does vmstat 10 say during these spikes? If you're running the
> sysstate service with data collection then sar can tell you a lot.
Henk seemed a bit confused about this suggestion, and the typo doesn't
help. You can install the sysstat package with:
# apt-get install sysstat
This allows collecting system load info data at regular periods,
automatically, and sar is the tool you can use to look at it. On Debian,
in order to get it to collect that information for you, I believe you just
need to do:
# dpkg-reconfigure sysstat
Then answer "yes" to "Do you want to activate sysstat's cron job?" This
will install a crontab file that collects all the data you need for sar to
work. You may need to restart the service after that. There's a useful
walkthrough for this at
http://www.linuxweblog.com/blogs/wizap/20080126/sysstat-ubuntu
--
* Greg Smith gsmith@gregsmith.com http://www.gregsmith.com Baltimore, MD
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: gsmith@gregsmith.com, scott.marlowe@gmail.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: <Pine.GSO.4.64.0808290020060.23621@westnet.com>
* 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