X-Original-To: pgsql-php-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id D42075E46C2 for ; Fri, 27 Aug 2004 04:10:19 -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 82672-07 for ; Fri, 27 Aug 2004 07:10:14 +0000 (GMT) Received: from candice.isogo.co.za (outsmtp.isogo.co.za [196.15.191.4]) by svr1.postgresql.org (Postfix) with ESMTP id EEC905E3639 for ; Fri, 27 Aug 2004 04:10:11 -0300 (ADT) Received: (qmail 26747 invoked by uid 1035); 27 Aug 2004 07:10:06 -0000 Received: from justin@isogo.co.za by mail by uid 89 with qmail-scanner-1.20rc3 (clamscan: 0.60. spamassassin: 2.60. Clear:RC:1:. Processed in 0.15696 secs); 27 Aug 2004 07:10:06 -0000 Received: from host29.isogo.co.za (HELO ?10.5.200.29?) (justin@isogo.co.za@196.15.191.29) by candice.echelon.z with RC4-MD5 encrypted SMTP; 27 Aug 2004 07:10:05 -0000 Message-ID: <412EDE4A.4090807@isogo.co.za> Date: Fri, 27 Aug 2004 09:10:02 +0200 From: Justin Wyer User-Agent: Mozilla Thunderbird 0.6 (Windows/20040502) X-Accept-Language: en-us, en MIME-Version: 1.0 To: oleg@ourmx.com, pgsql-php Subject: Re: [pgsql-hackers-win32] 8.0 beta1 and XP SP2 References: <1677078158.20040827052820@ourmx.com> In-Reply-To: <1677078158.20040827052820@ourmx.com> Content-Type: text/plain; charset=us-ascii; format=flowed 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/43 X-Sequence-Number: 2931 Oleg Letsinsky wrote: >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 :) > > What is the CPU load under 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. > > If pg_restore works prehaps it is not a PostgreSQL problem.... >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... > > Try mod your script to dump back to the mysql database. Check if you get weird performance issues doing that. I think assuming it is PostgreSQL at this point is jumping the gun. Maybe active states perl doesn't run so well on SP2, or it could even be mysql. >Thanks for any input > > Pleasure Regards Justin