| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | MARK CALLAGHAN <mdcallag(at)gmail(dot)com> |
| Cc: | pgsql-advocacy(at)postgresql(dot)org |
| Subject: | Re: Probable faq: need some benchmarks of pgsql vr.s mysql |
| Date: | 2010-11-17 23:52:07 |
| Message-ID: | 4CE46AA7.2040309@agliodbs.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy |
> There is an IO completion callback that is called when the read into
> the buffer pool is finished. AFAIK, the callback will merge the
> pending changes from the insert buffer. Oh, and the name of the insert
> buffer has been changed to "change buffer" as it can buffer inserts
> and deletes in MySQL 5.5. Also note that there are no updates for
> secondary indexes. There is only insert and delete marking.
Seems like it still needs work. I'm not entirely convinced that an
index buffer would be a net win for PostgreSQL, given the different
structure of our storage. I'd look at those "fractal indexes" first.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ken.Rosensteel | 2010-11-18 17:12:04 | Re: Postgres References |
| Previous Message | MARK CALLAGHAN | 2010-11-17 20:24:01 | Re: Probable faq: need some benchmarks of pgsql vr.s mysql |