PostgreSQL Indexing versus MySQL

From: "Chris Fossenier" <chris(at)engenuit(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: PostgreSQL Indexing versus MySQL
Date: 2004-02-11 20:58:54
Message-ID: 073f01c3f0e1$df78f560$e701a8c0@plinkplonk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I currently have a client with a database that must hold 125 million records
and all tallied about 250 fields.

The database has been normalized and indexed appropriately.

If any of you have worked with MySQL, you will have discovered that indexing
is very limited. You can only have one index file per table. The indexing
process actuallly creates a full copy of the original table and once you get
above 2 indexes with 125million records, it is extremely slow.

Should I even bother trying PostgreSQL to resolve this issue?

We can generate the same indexes in MS SQL and Oracle in a fraction of the
amount of time when held up to MySQL.

Thanks

Chris.

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Cyril VELTER 2004-02-11 21:08:03 Prepared queries
Previous Message Bruce Momjian 2004-02-11 20:21:32 Re: createdb feature request