On 5/28/15 9:31 AM, Ravi Krishna wrote:
> explain select count(*) from tstesting.account where account_row_inst = 101 ;
> Aggregate (cost=8.16..8.17 rows=1 width=0)
> -> Index Only Scan using account_pkey on account (cost=0.14..8.16
> rows=1 width=0)
> Index Cond: (account_row_inst = 101)
EXPLAIN only shows what the planner thinks a query will cost. For any
real testing, you need EXPLAIN ANALYZE.
Also, understand that partitioning isn't a magic bullet. It can make
some operations drastically faster, but it's not going to help every
scenario, and will actually slow some other operations down.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Data in Trouble? Get it in Treble! http://BlueTreble.com
