X-Original-To: pgsql-hackers-win32-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 8EFA03A584F; Thu, 2 Dec 2004 19:42:41 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75302-08; Thu, 2 Dec 2004 19:42:37 +0000 (GMT) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by svr1.postgresql.org (Postfix) with ESMTP id 9450C3A5875; Thu, 2 Dec 2004 19:42:38 +0000 (GMT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.1/8.13.1) with ESMTP id iB2Jgb7Y029327; Thu, 2 Dec 2004 14:42:38 -0500 (EST) To: Bruce Momjian Cc: Merlin Moncure , Dave Page , pgsql-performance@postgresql.org, Magnus Hagander , Win 32 hackers PGSQL Subject: Re: [PERFORM] scalability issues on win32 In-reply-to: <200412021928.iB2JSHo09487@candle.pha.pa.us> References: <200412021928.iB2JSHo09487@candle.pha.pa.us> Comments: In-reply-to Bruce Momjian message dated "Thu, 02 Dec 2004 14:28:17 -0500" Date: Thu, 02 Dec 2004 14:42:37 -0500 Message-ID: <29326.1102016557@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.002 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200412/6 X-Sequence-Number: 2517 Bruce Momjian writes: > Merlin Moncure wrote: >> Ok, I am starting to strongly suspect the statistics collector of >> various kinds of malfeasance. > OK, the big problem is that we are nearing RC1. We would like some > feedback on this as soon as possible. A major Win32 cleanup for this > could delay the 8.0 release. I would say that it shouldn't delay the release --- worst case, we say "the collector doesn't work very well under Win32 yet". It's probably not the only part of the system we'll find needs work under Win32. This is moot if Merlin can find some simple fixable bug, but I'm worried that doing anything significant might require major work. BTW, what about the issue we just identified with piperead() failing to set errno on Windows? That would certainly account for the "random collector restarts" complaint ... regards, tom lane