Re: Caching of Queries (now with pgpool)

From: Michael Adler <adler(at)pobox(dot)com>
To: Jason Coene <jcoene(at)gotfrag(dot)com>
Cc: "'Josh Berkus'" <josh(at)agliodbs(dot)com>, pgsql-performance(at)postgresql(dot)org, mendola(at)bigfoot(dot)com, tgl(at)sss(dot)pgh(dot)pa(dot)us
Subject: Re: Caching of Queries (now with pgpool)
Date: 2004-09-24 02:00:59
Message-ID: 20040924020058.GA11703@pobox.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Sep 23, 2004 at 09:23:51PM -0400, Jason Coene wrote:
> I ran some previous queries to get pgpool to pre-establish all the
> connections, and ab ran for a few minutes (with one query per page, eek!).
> It was still exhibiting the same problems as before. While so many new
> connections at once can surely make the problem worse (and pgpool will
> surely help there), shouldn't this prove that it's not the only issue?

> Any ideas?

Now that your connections are persistent, you may benefit from using
PREPAREd queries.

-Mike

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Mark Wong 2004-09-24 15:07:03 Re: O_DIRECT setting
Previous Message Jason Coene 2004-09-24 01:23:51 Re: Caching of Queries (now with pgpool)