| From: | David Fetter <david(at)fetter(dot)org> |
|---|---|
| To: | Dave Page <dpage(at)pgadmin(dot)org> |
| Cc: | Rob Wultsch <wultsch(at)gmail(dot)com>, John Gage <jsmgage(at)numericable(dot)fr>, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, "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 17:37:01 |
| Message-ID: | 20100625173700.GV1474@fetter.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Jun 25, 2010 at 09:44:04AM +0100, Dave Page wrote:
> It could also be argued that having a storage engine API means that
> the query planner/optimiser cannot have nearly as much knowledge
> about how the data is stored and what access characteristics it may
> have thus preventing it from being as well optimised as Postgres.
Having it divided off at the place where it's divided in MySQL is
certainly such a barrier. Having a storage API, as PostgreSQL used to
have, and will have again with SQL/MED, doesn't necessarily present
such a barrier.
Cheers,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com
iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics
Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate
| From | Date | Subject | |
|---|---|---|---|
| Next Message | RP Khare | 2010-06-25 17:54:04 | Backup issues |
| Previous Message | Michael Nolan | 2010-06-25 16:47:39 | Re: Equivalent to "use database" in postgre |