| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | "Ravindran G - TLS, Chennai(dot)" <ravindran_g(at)hcl(dot)in> |
| Cc: | Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-performance(at)postgresql(dot)org, "Isac Newton A - TLS, Chennai(dot)" <isacnewtona(at)hcl(dot)in> |
| Subject: | Re: Postgre SQL 7.1 cygwin performance issue. |
| Date: | 2006-08-28 14:56:46 |
| Message-ID: | 1156777006.3932.11.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2006-08-28 at 09:00, Ravindran G - TLS, Chennai. wrote:
> Thanks Alvaro.
>
> We are using PostgreSQL 7.1 cygwin installed on Windows 2000.
>
> We understand that the maximum connections that can be set is 64 in
> Postgresql 7.1 version.
>
> But our application is installed in 8 / 10 PC or more than that and it opens
> multiple connections and it exceeds 64.
>
> Because of this the subsequent connections are failed to connect with DB
> from application.
>
> Please advise us on how to resolve this ?.
As someone else mentioned, pg_pool might help here. But you're kind of
fighting an uphill battle here. I'm guessing that your effort will be
better spent on upgrading your db server than on trying to patch up the
system you have.
Is there any chance of changing your client app so it doesn't open so
many connections? That would seem the easiest fix of all, if you have
access to that code.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2006-08-28 15:09:19 | Re: Postgre SQL 7.1 cygwin performance issue. |
| Previous Message | Brad Nicholson | 2006-08-28 14:48:18 | Re: Identifying bloated tables |