Re: Using Index-only scans to speed up count(*) - Mailing list pgsql-hackers

From Noah Misch
Subject Re: Using Index-only scans to speed up count(*)
Date
Msg-id 20140607150410.GA509883@tornado.leadboat.com
Whole thread Raw
In response to Using Index-only scans to speed up count(*)  (Gurjeet Singh <gurjeet@singh.im>)
List pgsql-hackers
On Sat, Jun 07, 2014 at 08:35:27AM -0400, Gurjeet Singh wrote:
> While reading [1] in context of Postgres Hibernator, I see that
> Mitsuru mentioned one of the ways other RDBMS allows count(*) to be
> driven by an index.
> 
> > 'select /*+ INDEX(emp emp_pk) */ count(*) from emp;' to load index blocks
> 
> I am not sure if Postgres planner already allows this, 

It does:

create table t (c, junk) as select *, repeat('a', 100) from generate_series(1,10000);
alter table t add primary key (c);
vacuum t;
analyze t;
explain select count(*) from t;

-- 
Noah Misch
EnterpriseDB                                 http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Cédric Villemain
Date:
Subject: Re: Using Index-only scans to speed up count(*)
Next
From: Kevin Grittner
Date:
Subject: Re: PG Manual: Clarifying the repeatable read isolation example