Re: mysql to postgresql, performance questions

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Crooke <dcrooke(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, "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-24 00:01:56
Message-ID: dcc563d11003231701j4b9b2b98r34cc090bd1526a40@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Tue, Mar 23, 2010 at 5:35 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> writes:
>> On Tue, Mar 23, 2010 at 5:07 PM, Dave Crooke <dcrooke(at)gmail(dot)com> wrote:
>>> What about InnoDB?
>
>> Depends on what parts of mysql they otherwise use.  There are plenty
>> of features that won't work if you're using non-myisam tables, like
>> full text search.  I tend to think any full blown (or nearly so) db is
>> overkill for mythtv, and the use of something like sqllite or berkely
>> db tables is a better fit.
>
> That's apparently also the position of their lead developer; although
> considering he's not actually done anything about it for six or more
> years, it seems like quite a lame excuse for blocking ports to other
> DBs.

Methinks he's big on his "comfort-zone".

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Alvaro Herrera 2010-03-24 03:20:23 Re: tuning auto vacuum for highly active tables
Previous Message Scott Marlowe 2010-03-23 23:59:10 Re: tuning auto vacuum for highly active tables