For the record, the table we're having trouble inserting into is ~100 rows
with ~50 indexes on it. E.F Codd is spinning in his grave. The reason
they went with this design (instead of one that has two tables, each with
3-6 columns, and about that many indexes) is that "joins are slow".
Which they may be on Mysql, I don't know. But this is (unfortunately) a
different battle.
Brian
On Fri, 29 Oct 2010, Josh Berkus wrote:
> Brian,
>
> Rob pointed me to a benchmark of MySQL vs. Tokutek which is interesting
> to your case:
>
> http://www.mysqlperformanceblog.com/2009/04/28/detailed-review-of-tokutek-storage-engine/
>
> It's also interesting to me because apparently InnoDB *does* have an
> issue with large numbers of inserts to an already-large table, which we
> don't have (I don't think we do, anyway).
>
> --
> -- Josh Berkus
> PostgreSQL Experts Inc.
> http://www.pgexperts.com
>
> --
> Sent via pgsql-advocacy mailing list (pgsql-advocacy@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-advocacy
>