Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Abnormal performance difference between Postgres and MySQL
- From: Guillaume Smet <guillaume(dot)smet(at)gmail(dot)com>
- To: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
- Cc: Farhan Husain <russoue(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: Abnormal performance difference between Postgres and MySQL
- Date: Tue, 24 Feb 2009 00:33:33 +0100
- Message-id: <1d4e0c10902231533t1b3731cdnda3adff7dd9811bb@mail.gmail.com> <text/plain>
On Tue, Feb 24, 2009 at 12:27 AM, Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> wrote: > If it's not C then string compares are going to probably need special > indexes to work the way you expect them. (varchar pattern ops). Look > here for more information: > > http://www.postgresql.org/docs/8.3/static/indexes-opclass.html It's only relevant for pattern matching (eg LIKE or regexp). AFAICS, the OP only uses plain equals in his query. An EXPLAIN ANALYZE output would be nice to diagnose the problem. -- Guillaume
- Follow-Ups:
- Re: Abnormal performance difference between Postgres and MySQL
- From: Scott Marlowe
- Re: Abnormal performance difference between Postgres and MySQL
- References:
- Abnormal performance difference between Postgres and MySQL
- From: Farhan Husain
- Re: Abnormal performance difference between Postgres and MySQL
- From: Scott Marlowe
- Abnormal performance difference between Postgres and MySQL
- Prev by Date: Re: Abnormal performance difference between Postgres and MySQL
- Next by Date: Re: postgreSQL performance 8.2.6 vs 8.3.3
- Previous by thread: Re: Abnormal performance difference between Postgres and MySQL
- Next by thread: Re: Abnormal performance difference between Postgres and MySQL
- Indexes: