| From: | "Christopher Browne" <cbbrowne(at)gmail(dot)com> |
|---|---|
| To: | "Ravindran G - TLS, Chennai(dot)" <ravindran_g(at)hcl(dot)in>, 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:28:42 |
| Message-ID: | d6d6637f0608280728l2dc87be6m573fa31d7974bde6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 8/28/06, Alvaro Herrera <alvherre(at)commandprompt(dot)com> wrote:
> > Please advise us on how to resolve this ?.
>
> There's no solution short of upgrading.
That's a little too negative. There is at least one alternative,
possibly two...
1. Migrate the database to a Unix platform that does not suffer from
the Cygwin 64 connection restriction. (If running Linux, it may be
necessary to look for an old release, as there were changes to GLIBC
at around the same time as 7.2 that don't play perfectly well with
7.1...)
2. It is *possible* that pg_pool could be usable as a proxy that
limits the number of connections actually used. I'm not sure how well
it'll play with 7.1, mind you...
--
http://www3.sympatico.ca/cbbrowne/linux.html
Oddly enough, this is completely standard behaviour for shells. This
is a roundabout way of saying `don't use combined chains of `&&'s and
`||'s unless you think Gödel's theorem is for sissies'.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michal Taborsky - Internet Mall | 2006-08-28 14:39:30 | Identifying bloated tables |
| Previous Message | Alvaro Herrera | 2006-08-28 14:19:59 | Re: Postgre SQL 7.1 cygwin performance issue. |