Skip site navigation (1) Skip section navigation (2)

Re: mysql to postgresql, performance questions

From: Dave Crooke <dcrooke(at)gmail(dot)com>
To: Greg Smith <greg(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ross J(dot) Reedstrom" <reedstrm(at)rice(dot)edu>, pgsql-performance(at)postgresql(dot)org
Subject: Re: mysql to postgresql, performance questions
Date: 2010-03-23 23:07:07
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
What about InnoDB?

On Tue, Mar 23, 2010 at 4:38 PM, Greg Smith <greg(at)2ndquadrant(dot)com> wrote:

> 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
> , 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(at)2ndQuadrant(dot)com
> --
> Sent via pgsql-performance mailing list (pgsql-performance(at)postgresql(dot)org)
> To make changes to your subscription:

In response to


pgsql-performance by date

Next:From: Bhella Paramjeet-PFCW67Date: 2010-03-23 23:28:03
Subject: Re: tuning auto vacuum for highly active tables
Previous:From: Scott MarloweDate: 2010-03-23 21:41:48
Subject: Re: tuning auto vacuum for highly active tables

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group