| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Samuel Gendler <sgendler(at)ideasculptor(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Need help in performance tuning. |
| Date: | 2010-07-09 04:42:46 |
| Message-ID: | 8760.1278650566@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Samuel Gendler <sgendler(at)ideasculptor(dot)com> writes:
> On Thu, Jul 8, 2010 at 8:11 PM, Craig Ringer
> <craig(at)postnewspapers(dot)com(dot)au> wrote:
>> If you're not using a connection pool, start using one.
> I see this issue and subsequent advice cross this list awfully
> frequently. Is there in architectural reason why postgres itself
> cannot pool incoming connections in order to eliminate the requirement
> for an external pool?
Perhaps not, but there's no obvious benefit either. Since there's
More Than One Way To Do It, it seems more practical to keep that as a
separate problem that can be solved by a choice of add-on packages.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hannu Krosing | 2010-07-09 05:48:49 | Re: Need help in performance tuning. |
| Previous Message | Samuel Gendler | 2010-07-09 04:19:22 | Re: Need help in performance tuning. |