| From: | Rob Wultsch <wultsch(at)gmail(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, John Gage <jsmgage(at)numericable(dot)fr>, "Wang, Mary Y" <mary(dot)y(dot)wang(at)boeing(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Need Some Recent Information on the Differences between Postgres and MySql |
| Date: | 2010-06-25 16:05:56 |
| Message-ID: | AANLkTikaeL5XqiLSg0vyUTsq3E8k3gOd-fKwu8I80NP6@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 25, 2010 at 8:56 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote:
> On Fri, Jun 25, 2010 at 11:48 AM, Rob Wultsch <wultsch(at)gmail(dot)com> wrote:
>> - Innodb : The primary transactional storage engine for MySQL. It does
>> not have all the features of PG (like check contraints), but it has
>> some features (like Compression!!!) which are *exceptionally* useful.
>
> You do know that pg has compression for text types built in already,
> right? I'm sure there are subtle differences in the way compression
> is done in each engine, just pointing that out.
>
I do, but TOAST is a very different animal than compression at the
page level. The innodb buffer pool is also effectively compressed
which allows for far greater use of memory.
--
Rob Wultsch
wultsch(at)gmail(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A.M. | 2010-06-25 16:28:24 | Re: flatten pg_auth_members |
| Previous Message | Dennis C | 2010-06-25 16:04:08 | Re: PG dump and restore |