| 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:38:47 |
| Message-ID: | 4B94C5A7.2090308@cs.helsinki.fi |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-advocacy pgsql-hackers |
On 2010-03-08 11:17 +0200, Pierre C wrote:
> - index skip scans (well, MySQL doesn't really do index skip scans, but
> since it can do index-only scans, it's an approximation)
As far as I can tell, we already do index skip scans:
=> create index foo_a_b_idx on foo(a,b);
CREATE INDEX
=> explain analyze select * from foo where b = 2;
QUERY PLAN
---------------------------------------------------------------------------
Index Scan using foo_a_b_idx on foo (cost=0.00..20.30 rows=5 width=8)
(actual time=0.027..0.057 rows=1 loops=1)
Index Cond: (b = 2)
Total runtime: 0.075 ms
(3 rows)
Regards,
Marko Tiikkaja
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre C | 2010-03-08 09:47:47 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Pierre C | 2010-03-08 09:17:55 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pierre C | 2010-03-08 09:47:47 | Re: SQL compatibility reminder: MySQL vs PostgreSQL |
| Previous Message | Tim Bunce | 2010-03-08 09:36:32 | Re: Core dump running PL/Perl installcheck with bleadperl [PATCH] |