Re: Caching of Queries

From: Matt Clark <matt(at)ymogen(dot)net>
To: "Jim C(dot) Nasby" <decibel(at)decibel(dot)org>
Cc: Postgresql Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Caching of Queries
Date: 2004-10-01 05:43:42
Message-ID: 415CEE8E.8060805@ymogen.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


>If you're not using a connection pool of some kind then you might as
>well forget query plan caching, because your connect overhead will swamp
>the planning cost. This does not mean you have to use something like
>pgpool (which makes some rather questionable claims IMO); any decent web
>application language/environment will support connection pooling.
>
>
Hmm, a question of definition - there's a difference between a pool and
a persistent connection. Pretty much all web apps have one connection
per process, which is persistent (i.e. not dropped and remade for each
request), but not shared between processes, therefore not pooled.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Dustin Sallings 2004-10-01 06:30:49 inconsistent/weird index usage
Previous Message Jim C. Nasby 2004-09-30 22:11:07 Re: Caching of Queries