From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | mlw <markw(at)mohawksoft(dot)com> |
Cc: | owensmk(at)earthlink(dot)net, pgsql-hackers(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Connection Pooling, a year later |
Date: | 2001-12-18 03:42:03 |
Message-ID: | 200112180342.fBI3g4s23880@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> I don't get the deal with connection pooling.
>
> Sure, there are some efficiencies in reducing the number of
> back-end postgres processes, but at what I see as a huge
> complication.
>
> Having experimented with Oracle's connection pooling, and watching
> either it or PHP(Apache) crash because of a bug in the query
> state tracking, I figured I'd buy some more RAM and forget about
> the process memory and call myself lucky.
>
> If you have a web server and use (in PHP) pg_pConnect, you will
> get a postgresql process for each http process on your web
> servers.
>
> Beside memory, are there any real costs associated with having
> a good number of idle PostgreSQL processes sitting around?
I think it is the startup cost that most people want to avoid, and our's
is higher than most db's that use threads; at least I think so.
It would just be nice to have it done internally rather than have all
the clients do it, iff it can be done cleanly.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | mlw | 2001-12-18 03:50:24 | Re: Connection Pooling, a year later |
Previous Message | Tom Lane | 2001-12-18 03:29:01 | Deadlock condition in current sources |