From: | Markus Schaber <schabi(at)logix-tt(dot)com> |
---|---|
To: | Magnus Hagander <mha(at)sollentuna(dot)net> |
Cc: | Pgsql performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Inserts optimization? |
Date: | 2006-04-19 12:08:41 |
Message-ID: | 44462849.3070209@logix-tt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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?
<cynism>
Now, I understand how the mysql people manage to spread the legend of
mysql being fast. They convince software developers to thwart all others.
</>
Seriously: How can we convince developers to either fix MySQL or abandon
and replace it with a database, instead of crippling client software?
> Actually, it might well hurt by introducing extra delays.
Well, if you read the documentation, you will see that it will only wait
if there are at least commit_siblings other transactions active. So when
Bacula serializes access, there will be no delays, as there is only a
single transaction alive.
HTH
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2006-04-19 12:11:06 | Re: Inserts optimization? |
Previous Message | Theo Kramer | 2006-04-19 09:26:00 | Re: Multicolumn order by |