Re: Caching of Queries

From: Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>
To: matt(at)ymogen(dot)net
Cc: pg(at)rbt(dot)ca, awerman2(at)hotmail(dot)com, scottakirkwood(at)gmail(dot)com, pgsql-performance(at)postgresql(dot)org
Subject: Re: Caching of Queries
Date: 2004-10-03 15:28:23
Message-ID: 20041004.002823.85416338.t-ishii@sra.co.jp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

> >>More to the point though, I think this is a feature that really really
> >>should be in the DB, because then it's trivial for people to use.
> >>
> >>
> >
> >How does putting it into PGPool make it any less trivial for people to
> >use?
> >
> The answers are at http://www2b.biglobe.ne.jp/~caco/pgpool/index-e.html
> . Specifically, it's a separate application that needs configuration,
> the homepage has no real discussion of the potential pitfalls of pooling
> and what this implementation does to get around them, you get the idea.

I don't know what you are exactly referring to in above URL when you
are talking about "potential pitfalls of pooling". Please explain
more.
--
Tatsuo Ishii

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Pierre-Frédéric Caillaud 2004-10-03 15:29:37 Re: index not used when using function
Previous Message Pierre-Frédéric Caillaud 2004-10-03 13:30:05 Re: Caching of Queries