X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id EC3B5538BE for ; Thu, 14 Apr 2005 19:01:30 -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 46583-07 for ; Thu, 14 Apr 2005 22:01:19 +0000 (GMT) Received: from vms040pub.verizon.net (vms040pub.verizon.net [206.46.252.40]) by svr1.postgresql.org (Postfix) with ESMTP id 35C6A538AA for ; Thu, 14 Apr 2005 19:01:18 -0300 (ADT) Received: from jfradkin ([63.162.100.127]) by vms040.mailsrvcs.net (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004)) with ESMTPA id <0IEY004F9II7ZUDA@vms040.mailsrvcs.net> for pgsql-performance@postgresql.org; Thu, 14 Apr 2005 17:01:20 -0500 (CDT) Date: Thu, 14 Apr 2005 18:01:19 -0400 From: "Joel Fradkin" Subject: Re: speed of querry? In-reply-to: <000901c54110$79032aa0$797ba8c0@jfradkin> To: "'Tom Lane'" , "'Dawid Kuroczko'" Cc: "'PERFORM'" Message-id: <000001c5413d$7d9897d0$797ba8c0@jfradkin> MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2180 X-Mailer: Microsoft Outlook, Build 10.0.6626 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: quoted-printable Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200504/319 X-Sequence-Number: 11716 Well so far I have 1.5 hours with commandpromt.com and 8 + hours with = Dell and have not seen any changes in the speed of my query. I did move the data base to the raid 5 drives and did see a 1 second improvement from 13 secs to 12 secs (keep in mind it runs in 6 on the optiplex). The dell guy ran Bonie and found 40meg per sec read/write speed for the arrays. He also installed version 8.0.2 (went fine on AS4 he had to uninstall = 8.0.1 first). He is going to get a 6650 in his test lab to see what he can fugure out. I will say both commandprompt.com and Dell have been very professional = and I am impressed at the level of support available for Redhat from Dell and postgres. As always I still feel this list has been my most useful = asset, but I am glad there are folks to call on. I am trying to go live soon = and need to get this resolved. I told the guy from Dell it makes no sense that a windows 2.4 single = proc with 750 meg of ram can go faster then a 4 proc (3.ghz) 8 gig machine. Both databases were restored from the same file. Same view etc. Config files are set the same except for amount of cached ram, although Commandprompt.com had me adjust a few items that should help going into production, put planning stuff is basicly the same. This view returns in 3 secs on MSSQL server on the optiplex (750 meg 2.4 box); and 6 secs using postgres on windows and 12-13 secs on the 4 = processor box. Needless to say I am very frustrated. Maybe Dell will turn up = something testing in their lab. It took a bit of perseverance to get to the right = guy at Dell (the first guy actually told me to load it all on a like machine = and if it was very much slower on my original they would pursue it otherwise = it was not an issue. I was like the machine cost 30K you going to send me = one to test that. But seriously I am open to trying anything (loading AS3, = using postgres 7.4)? The fellow at Dell does not think it is a hardware = problem, so if it is Linux (could very well be, but he seemed very sharp and did = not come up with anything yet) or postgres config (again Josh at commandprompt.com was very sharp) then what do I do now to isolate the issue? At least they are loading one in the lab (in theory, I cant send = them my database, so who knows what they will test). Dell changed the file = system to ext2 is that going to bite me in the butt? It did not seem to change = the speed of my explain analyze. Joel Fradkin =20 Dawid Kuroczko writes: > Basically it tells postgres how many values should it keep for > statistics per column. The config default_statistics_target > is the default (=3D used when creating table) and ALTER... is > a way to change it later. Not quite. default_statistics_target is the value used by ANALYZE for any column that hasn't had an explicit ALTER SET STATISTICS done on it. So you can change default_statistics_target and that will affect existing tables. (It used to work the way you are saying, but that was a few releases back...) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly