Re: SQL compatibility reminder: MySQL vs PostgreSQL

From: "Pierre C" <lists(at)peufeu(dot)com>
To: "Marko Tiikkaja" <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi>
Cc: francois(dot)perou(at)free(dot)fr, "Josh Berkus" <josh(at)agliodbs(dot)com>, "Craig Ringer" <craig(at)postnewspapers(dot)com(dot)au>, "Andrew Dunstan" <andrew(at)dunslane(dot)net>, pgsql-hackers(at)postgresql(dot)org, dpage(at)pgadmin(dot)org
Subject: Re: SQL compatibility reminder: MySQL vs PostgreSQL
Date: 2010-03-08 10:06:50
Message-ID: op.u88udovueorkce@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-hackers


> Oh, this is what I believe MySQL calls "loose index scans". I'm

Exactly :
http://dev.mysql.com/doc/refman/5.0/en/loose-index-scan.html

> actually looking into this as we speak,

Great ! Will it support the famous "top-n by category" ?

> but there seems to be a
> non-trivial amount of work to be done in order for this to work.
>
>
> Regards,
> Marko Tiikkaja

In response to

Browse pgsql-advocacy by date

  From Date Subject
Next Message Robert Haas 2010-03-08 14:44:51 Re: SQL compatibility reminder: MySQL vs PostgreSQL
Previous Message Marko Tiikkaja 2010-03-08 09:58:26 Re: SQL compatibility reminder: MySQL vs PostgreSQL

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2010-03-08 10:08:24 Re: Visual Studio 2005, C-language function - avoiding hacks?
Previous Message Magnus Hagander 2010-03-08 10:03:51 Re: psql with GSS can crash