| From: | Scott Marlowe <smarlowe(at)g2switchworks(dot)com> |
|---|---|
| To: | Markus Schaber <schabi(at)logix-tt(dot)com> |
| Cc: | Magnus Hagander <mha(at)sollentuna(dot)net>, Pgsql performance <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: Inserts optimization? |
| Date: | 2006-04-19 15:22:10 |
| Message-ID: | 1145460130.23538.119.camel@state.g2switchworks.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Wed, 2006-04-19 at 07:08, Markus Schaber wrote:
> Hi, Magnus,
>
> Magnus Hagander wrote:
>
> > Bacula already serializes access to the database (they have to support
> > mysql/myisam), so this shouldn't help.
>
> Ouch, that hurts.
>
> To support mysql, they break performance for _every other_ database system?
Note that should be "to support MySQL with MyISAM tables".
If they had written it for MySQL with innodb tables they would likely be
able to use the same basic methods for performance tuning MySQL as or
Oracle or PostgreSQL.
It's the refusal of people to stop using MyISAM table types that's the
real issue.
Of course, given the shakey ground MySQL is now on with Oracle owning
innodb...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-19 15:31:19 | Re: Inserts optimization? |
| Previous Message | Tom Lane | 2006-04-19 15:14:52 | Re: Inserts optimization? |