Received: from maia.hub.org (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 15C9C632817 for ; Tue, 23 Mar 2010 18:38:24 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 96082-08 for ; Tue, 23 Mar 2010 21:38:14 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mail.postgresql.org (Postfix) with ESMTP id 1AA4063271B for ; Tue, 23 Mar 2010 18:38:14 -0300 (ADT) Received: from [192.168.1.6] (pool-96-244-14-10.bltmmd.fios.verizon.net [96.244.14.10]) by mrelayeu.kundenserver.de (node=mrbap0) with ESMTP (Nemesis) id 0MHrmH-1Nsosx3fMj-004H9F; Tue, 23 Mar 2010 22:38:06 +0100 Message-ID: <4BA934B9.9070401@2ndquadrant.com> Date: Tue, 23 Mar 2010 17:38:01 -0400 From: Greg Smith User-Agent: Thunderbird 2.0.0.23 (X11/20090817) MIME-Version: 1.0 To: Tom Lane CC: "Ross J. Reedstrom" , pgsql-performance@postgresql.org Subject: Re: mysql to postgresql, performance questions References: <4BA23936.2030507@gmail.com> <4BA596D2.4050406@squeakycode.net> <20100323185232.GD6662@rice.edu> <5342.1269372121@sss.pgh.pa.us> In-Reply-To: <5342.1269372121@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V01U2FsdGVkX18YKRTqGaestb6Cm+eN688ZPogPlx2IIGP+ZZG UliZrhCWCSVnzFE1ZY1ASUVpKP3XI9pAam2o7SLdKdE+nrFlGR KAjaRCK/4TBm23N8V7BI2EgQsaFuK92 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-2.599 tagged_above=-10 required=5 tests=BAYES_00=-2.599 X-Spam-Level: X-Archive-Number: 201003/296 X-Sequence-Number: 38121 Tom Lane wrote: > So has anyone looked at porting MythTV to PG? > Periodically someone hacks together something that works, last big effort I'm aware of was in 2006, and then it bit rots away. I'm sure we'd get some user uptake on the result--MySQL corruption is one of the top ten cause of a MythTV system crashing. The developers are so resistant to database-neutral design that you'd need quite the thick skin to try and get something into their mainline though, which means someone who tried adding PostgreSQL support would likely have to run a parallel branch for some time, expecting regular breakage. The only thing on their radar as far as I know is SQLite. There was a good overview circa 2004 at http://david.hardeman.nu/files/patches/mythtv/mythletter.txt , haven't done a deep dive into the code recently enough to comment on exactly what has changed since then. That gives a flavor for the fundamentals of the design issues though. -- Greg Smith 2ndQuadrant US Baltimore, MD PostgreSQL Training, Services and Support greg@2ndQuadrant.com www.2ndQuadrant.us