X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id 42C17545E9 for ; Fri, 4 Mar 2005 23:21:02 +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 33022-01 for ; Fri, 4 Mar 2005 23:20:53 +0000 (GMT) Received: from boutiquenumerique.com (boutiquenumerique.com [82.67.9.10]) by svr1.postgresql.org (Postfix) with ESMTP id EB69652A4D for ; Fri, 4 Mar 2005 23:20:51 +0000 (GMT) Received: (qmail 19836 invoked from network); 5 Mar 2005 00:21:39 +0100 Received: from unknown (HELO musicbox) (boutiquenumerique-lists@192.168.0.2) by boutiquenumerique.com with SMTP; 5 Mar 2005 00:21:39 +0100 To: "Mauro Bertoli" , "Richard Huxton" Cc: pgsql-sql@postgresql.org Subject: Re: Postgres performance References: <20050302112456.79149.qmail@web51406.mail.yahoo.com> Message-ID: Date: Sat, 05 Mar 2005 00:20:54 +0100 From: PFC Organization: =?iso-8859-15?Q?La_Boutique_Num=E9rique?= Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit In-Reply-To: <20050302112456.79149.qmail@web51406.mail.yahoo.com> User-Agent: Opera M2/7.54u1 (Linux, build 892) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0.004 tagged_above=0 required=5 tests=AWL X-Spam-Level: X-Archive-Number: 200503/70 X-Sequence-Number: 20549 > I don't require transaction because the query aren't > complex and update a single tuple (in SELECT > transactions are useless) You mean, you have no foreign keys in your database ? In SELECT they are definitely useful (think select for update, isolation level serializable...) > - start quote - > You'll find inserts/updates with lots of users is > where PostgreSQL works > well compared to other systems. > - end quote - > Uhhmm.. this is interesting... pg does not lock the whole table everytime anyone wants to write in it. In MySQL when you run a big select, all write activity stops during that. If you run a big update, all activity other than this update has to wait. > - why postgres use a new process for every query ? > (mySQL, if I'm not wrong, use threads... I think its > faster) Not for every query, for every CONNECTION. You are using persistant connections are you. Are you ? > - why connection time is slower? (compared to mySQL)? This is of no importance as everyone uses persistent connections anyway. > - why postgres require analyze? (mySQL, if I'm not > wrong, don't require it) > Yours answers will be very apreciated! Thx So it has a planner which knows what it's doing ;) instead of just guessing in the dark. And MySQL requires analyze too (read the docs), optimize table which looks like vacuum to me, and sometimes repair table...