From: | Dave Page <dpage(at)pgadmin(dot)org> |
---|---|
To: | Ron Mayer <rm_pg(at)cheapcomplexdevices(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Understanding PostgreSQL Storage Engines |
Date: | 2010-10-13 11:35:57 |
Message-ID: | AANLkTin56Yvwtv=xXLm-B6J440vxiHvy7J76BQ=EM4ou@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Oct 13, 2010 at 12:29 PM, Ron Mayer
<rm_pg(at)cheapcomplexdevices(dot)com> wrote:
> Pavel Stehule wrote:
>> 2010/10/8 Carlos Mennens <carlos(dot)mennens(at)gmail(dot)com>:
>>> I know that MySQL uses MyISAM storage engine by default... what
>>> storage engine does PostgreSQL use by default ...
>>
>> PostgreSQL supports and uses just only one storage engine - PostgreSQL.
>
> That said, ISTM one of Postgres's bigger strengths commercially seems
> to be that vendors can reasonably easily plug in different storage engines.
That depends on how you define "reasonably easily". It's not even
remotely close to the ease with which you can plugin a different
storage engine in MySQL, and would take a significant amount of
engineering expertise and effort.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2010-10-13 12:11:18 | Re: Understanding PostgreSQL Storage Engines |
Previous Message | Ron Mayer | 2010-10-13 11:29:03 | Re: Understanding PostgreSQL Storage Engines |