Whoops, turns out it doesn't work on both development machines, only one
of them. And the production machine and development machine that doesn't
work have this in common: they are both multiprocessors (two
hyperthreaded processors to be precise, so windows sees 4 cpus).
I tried setting the cygserver process to have an affinity for only one
cpu but the problem still arose.
David Mitchell wrote:
I've built postgres to run on cygserver rather than cygipc because we
were experiencing hangs that had previously been thought to be caused by
cygipc. After building postgres it worked fine under heavy load on my
workstation, and both our development machines. However, once deployed
to our production server the problem reappeared.
What can I do to alleviate this problem?
--
David Mitchell
Software Engineer
Telogis
NOTICE:
This message (including any attachments) contains CONFIDENTIAL
INFORMATION intended for a specific individual and purpose, and
is protected by law. If you are not the intended recipient,
you should delete this message and are hereby notified that any
disclosure, copying, or distribution of this message, or the
taking of any action based on it, is strictly prohibited.
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
|
