| From: | Marko Tiikkaja <marko(dot)tiikkaja(at)cs(dot)helsinki(dot)fi> |
|---|---|
| To: | Pierre C <lists(at)peufeu(dot)com> |
| 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 09:58:26 |
| Message-ID: | 4B94CA42.3090909@cs.helsinki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
On 2010-03-08 11:47 +0200, Pierre C wrote:
>> As far as I can tell, we already do index skip scans:
>
> This feature is great but I was thinking about something else, like SELECT
> DISTINCT, which currently does a seq scan, even if x is indexed.
>
> Here is an example. In both cases it could use the index to skip all
> non-interesting rows, pulling only 69 rows from the heap instead of 120K.
Oh, this is what I believe MySQL calls "loose index scans". I'm
actually looking into this as we speak, but there seems to be a
non-trivial amount of work to be done in order for this to work.
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre C | 2010-03-08 10:06:50 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Pierre C | 2010-03-08 09:47:47 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2010-03-08 10:03:51 | Re: psql with GSS can crash |
| Previous Message | Pierre C | 2010-03-08 09:47:47 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |