Re: Shared buffers, db transactions commited, and write IO on Solaris - Mailing list pgsql-performance

From Josh Berkus
Subject Re: Shared buffers, db transactions commited, and write IO on Solaris
Date
Msg-id 200704030926.02946.josh@agliodbs.com
Whole thread Raw
In response to Re: Shared buffers, db transactions commited, and write IO on Solaris  (Erik Jones <erik@myemma.com>)
List pgsql-performance
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

pgsql-performance by date:

Previous
From: Guillaume Cottenceau
Date:
Subject: Re: Cache hit ratio
Next
From: "Alex Deucher"
Date:
Subject: Re: postgres 7.4 vs 8.x redux: query plans