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 D75E75E37D0 for ; Thu, 26 Aug 2004 22:28:15 -0300 (ADT) 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 92959-07 for ; Fri, 27 Aug 2004 01:28:13 +0000 (GMT) Received: from ourmx.com (ourmx.com [69.55.224.48]) by svr1.postgresql.org (Postfix) with ESMTP id 1EB275E3632 for ; Thu, 26 Aug 2004 22:28:11 -0300 (ADT) Received: from gateway.localdomain (ppp4-37.pppoe.mtu-net.ru [81.195.4.37]) by ourmx.com (Postfix) with ESMTP id 0097A17CB5 for ; Thu, 26 Aug 2004 18:28:15 -0700 (PDT) Received: from avenger (avenger [192.168.0.2]) by gateway.localdomain (Postfix) with ESMTP id 39390617800 for ; Fri, 27 Aug 2004 05:28:13 +0400 (MSD) Date: Fri, 27 Aug 2004 05:28:20 +0400 From: Oleg Letsinsky X-Mailer: The Bat! (v2.12.00) Business Reply-To: oleg@ourmx.com Organization: (none) X-Priority: 3 (Normal) Message-ID: <1677078158.20040827052820@ourmx.com> To: PgSQL Win32 developers Subject: 8.0 beta1 and XP SP2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests= X-Spam-Level: X-Archive-Number: 200408/424 X-Sequence-Number: 2102 Hi, I'm wondering if anyone has tried running PgSQL on XP SP2? I have a problem with it - quite a big one. I have a perl DBI script which is a migration tool from old MySQL database format to a new PgSQL database. So here is a quick summary of the situation. MySQL (win32) - perl - PgSQL (Linux server) Runs fine, full speed, the script finishes its work in 20 minutes. Next, I move PgSQL to the windows side. MySQL (win32) - perl - PgSQL (win32, XP SP1) Runs fine, just a bit slower (like 25 minutes) In both previous cases there were 100% CPU load, HD activity, etc. - two databases raping poor windows XP workstation. Next, after SP2 installation - that's here the fun comes. The process can take hours to complete. Actually, I never had a patience to see it finished - last time I aborted the process after 2 hours and the damn thing just finished about 50% of its job. I switched PgSQL back to Linux without changing anything else - no performance problems. I uninstalled SP2 and checked again - all is ok, all goes full speed, 25 minutes for task completion. Reinstalled SP2 - and the problem came back. So for me it's quite obvious that SP2 has screwed up PgSQL in some way. I've tried several web forums, IRC - so far nobody seems to get into the same situation since I'm likely to be the only PgSQL user stupid enough to try SP2 :) Now some details on what script does. It's, like I said, a migration script - it takes data from one database, changes it slightly and puts it to another one, using simple inserts. Nothing special. Although pg_restore seems to work just fine even under SP2, no performance problems. There's more. I've tried PowerGres database as well. It experiences the same performance hit, no difference at all. Some details on the system - WinXP Pro, P4 2.4Ghz, 1GB RAM, 200GB SATA Seagate drive. I've disabled that firewall thingy and data execution prevention - again, nothing has changed. I'm out of ideas... Thanks for any input -- Oleg Letsinsky, Software Developer