X-Original-To: pgsql-performance-postgresql.org@localhost.postgresql.org Received: from localhost (developer.postgresql.org [64.117.224.193]) by svr1.postgresql.org (Postfix) with ESMTP id 983CAB439AE for ; Fri, 4 Jul 2003 11:12:37 +0000 (GMT) Received: from svr1.postgresql.org ([64.117.224.193]) by localhost (svr1.postgresql.org [64.117.224.193]) (amavisd-new, port 10024) with ESMTP id 45554-07 for ; Fri, 4 Jul 2003 08:12:27 -0300 (ADT) Received: from anchor-post-35.mail.demon.net (anchor-post-35.mail.demon.net [194.217.242.85]) by svr1.postgresql.org (Postfix) with ESMTP id 01903B43A18 for ; Fri, 4 Jul 2003 08:12:27 -0300 (ADT) Received: from mwynhau.demon.co.uk ([193.237.186.96] helo=mainbox.archonet.com) by anchor-post-35.mail.demon.net with esmtp (Exim 3.36 #2) id 19YOUO-0004ED-0Z; Fri, 04 Jul 2003 12:12:29 +0100 Received: from localhost (localhost.localdomain [127.0.0.1]) by mainbox.archonet.com (Postfix) with ESMTP id D1CD11628C; Fri, 4 Jul 2003 12:12:27 +0100 (BST) Received: from client.archonet.com (client.archonet.com [192.168.1.16]) by mainbox.archonet.com (Postfix) with ESMTP id 358A816285; Fri, 4 Jul 2003 12:12:27 +0100 (BST) Content-Type: text/plain; charset="iso-8859-1" From: Richard Huxton Organization: Archonet Ltd To: Rafal Kedziorski , pgsql-performance@postgresql.org Subject: Re: PostgreSQL vs. MySQL Date: Fri, 4 Jul 2003 12:12:25 +0100 User-Agent: KMail/1.4.3 References: <5.2.0.9.0.20030704120150.02eafda8@mail.polonium.de> In-Reply-To: <5.2.0.9.0.20030704120150.02eafda8@mail.polonium.de> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Message-Id: <200307041212.25289.dev@archonet.com> X-Virus-Scanned: by AMaViS snapshot-20020531 X-Archive-Number: 200307/47 X-Sequence-Number: 2340 On Friday 04 Jul 2003 11:03 am, Rafal Kedziorski wrote: > Hi, > > has anybody tested PostgreSQL 7.3.x tables agains MySQL 4.0.12/13 with > InnoDB? Lots of people probably. The big problem is that unless the tester's setup= =20 matches your intended usage the results are of little worth. For the tests to be meaningful, you need the same: - hardware - OS - query complexity - usage patterns - tuning options I'd suggest running your own tests with real data where possible. Just to m= ake=20 the situation more interesting, the best way to solve a problem in PG isn't= =20 necessarily the same in MySQL.