| From: | "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-performance(at)postgresql(dot)org>, "Richard Huxton" <dev(at)archonet(dot)com>, "Josep Maria Pinyol Fontseca" <jmpinyol(at)endepro(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Windows performance again |
| Date: | 2005-12-21 18:40:09 |
| Message-ID: | 6EE64EF3AB31D5448D0007DD34EEB3417DDBA4@Herge.rcsinc.local |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
> > It's *got* to be the network configuration on the client machine.
>
> We've seen gripes of this sort before --- check the list archives for
> possible fixes. I seem to recall something about a "QoS patch", as
> well as suggestions to get rid of third-party packages that might be
> interfering with the TCP stack.
I personally checked out the last report from a poster who got the issue
on win2k but not on winxp. I ran his exact dump into my 2k server with
no problems. This is definitely some type of local issue.
Josep: does your table have any large ( > 1k ) fields in it?
Merlin
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Fuhr | 2005-12-21 18:51:02 | Re: Wrong index used when ORDER BY LIMIT 1 |
| Previous Message | Carlos Benkendorf | 2005-12-21 18:16:01 | ORDER BY costs |