| From: | Josh Berkus <josh(at)agliodbs(dot)com> | 
|---|---|
| To: | pgsql-performance(at)postgresql(dot)org | 
| Subject: | Re: Shared buffers, db transactions commited, and write IO on Solaris | 
| Date: | 2007-04-03 16:26:02 | 
| Message-ID: | 200704030926.02946.josh@agliodbs.com | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alex Deucher | 2007-04-03 16:37:49 | Re: postgres 7.4 vs 8.x redux: query plans | 
| Previous Message | Luke Lonergan | 2007-04-03 16:17:47 | Re: Cache hit ratio |