X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id 794D99DC829 for ; Tue, 14 Mar 2006 17:10:53 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 24244-01 for ; Tue, 14 Mar 2006 17:10:53 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id BB69F9DC818 for ; Tue, 14 Mar 2006 17:10:50 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id 5A75F56427; Tue, 14 Mar 2006 15:10:52 -0600 (CST) Received: (hashcash-sendmail, from uid 1001); Tue, 14 Mar 2006 15:10:51 -0600 Date: Tue, 14 Mar 2006 15:10:51 -0600 From: "Jim C. Nasby" To: andremachado Cc: pgsql-performance@postgresql.org Subject: Re: firebird X postgresql 8.1.2 windows, performance comparison Message-ID: <20060314211050.GU45250@pervasive.com> References: <20060314120200.M31128@techforce.com.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20060314120200.M31128@techforce.com.br> X-Operating-System: FreeBSD 6.0-RELEASE-p4 amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Hashcash: 1:20:060314:andremachado@techforce.com.br::YESpiXCiPUcH6uvB:00000000 000000000000000000000000CvMx X-Hashcash: 1:20:060314:pgsql-performance@postgresql.org::sgTrNscoBXaNOr1u:00000 0000000000000000000000001gT/ X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.109 required=5 tests=[AWL=0.109] X-Spam-Score: 0.109 X-Spam-Level: X-Archive-Number: 200603/198 X-Sequence-Number: 17635 On Tue, Mar 14, 2006 at 09:02:49AM -0300, andremachado wrote: > Hello, > Attached is a file containing the problematic queries cited yesterday, with > "explain", "\di" and "show all" outputs. > The first one finished in almost 4 hours. Firebird for windows finished in 1m30s. > The second one CRASHED after some hours, without finishing. The error message > is at the file too. PANIC: could not open file "pg_xlog/0000000100000018000000E7" (log file 24, segment 231): Invalid argument IIRC that means you have a data corruption issue. As for the queries, EXPLAIN ANALYZE would be in order here. It looks like the first one might benefit from increasing work_memory. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461