| From: | Frank Wiles <frank(at)wiles(dot)org> |
|---|---|
| To: | "Dave Dutcher" <dave(at)tridecap(dot)com> |
| Cc: | mjs_ops(at)gmx(dot)net, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [PERFORMANCE] Stored Procedures |
| Date: | 2006-01-23 17:25:26 |
| Message-ID: | 20060123112526.1ee25dcd.frank@wiles.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 23 Jan 2006 10:23:17 -0600
"Dave Dutcher" <dave(at)tridecap(dot)com> wrote:
> I don't think pgpool is what you need. If I understand pgpool
> correctly, pgpool lets you pool multiple postgres servers together.
> You are just looking for database connection pooling.
While pgpool can let you pool together multiple backend servers,
it also functions well as just a connection pooling device with
only one backend.
---------------------------------
Frank Wiles <frank(at)wiles(dot)org>
http://www.wiles.org
---------------------------------
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-01-23 19:19:14 | Re: Slow queries consisting inner selects and order bys & hack to speed up |
| Previous Message | Dave Dutcher | 2006-01-23 16:23:17 | Re: [PERFORMANCE] Stored Procedures |