From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: Shared buffers, db transactions commited, and write IO on Solaris
Date: Tue, 3 Apr 2007 09:26:02 -0700
Message-ID: <200704030926.02946.josh@agliodbs.com> (raw)
In-Reply-To: <E64D7843-51F0-4288-80EC-8920147E333F@myemma.com>
References: <9B7F4B34-7E96-4501-BCE0-D0BED739530A@myemma.com>
<200703301446.35858.josh@agliodbs.com>
<E64D7843-51F0-4288-80EC-8920147E333F@myemma.com>
Erik,
> Well, our application code itself doesn't retry queries if the db is
> taking a long time to respond. However, we do have a number of our
> servers making db connections via pgpool so you may be on to
> something here. While I will be taking these questions to the pgpool
> lists, I'll posit them here as well: If a pgpool child process
> reaches it's connection lifetime while waiting on a query to
> complete, does pgpool retry the query with another child? If a
> connection thus dies, does the transaction complete normally on the
> server? If the answers to these questions are both yes, this could
> definitely be what was happening.
It's been a while since I used pgpool with load balancing turned on, so you
should probably try the pgpool lists. What version?
--
Josh Berkus
PostgreSQL @ Sun
San Francisco
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: josh@agliodbs.com
Subject: Re: Shared buffers, db transactions commited, and write IO on Solaris
In-Reply-To: <200704030926.02946.josh@agliodbs.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