From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Ravi Krishna <sravikrishna3(at)gmail(dot)com>, <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: Partitioning and performance |
Date: | 2015-05-28 18:05:34 |
Message-ID: | 556758EE.6000503@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
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
From | Date | Subject | |
---|---|---|---|
Next Message | Peter J. Holzer | 2015-05-29 08:55:44 | Different plan for very similar queries |
Previous Message | Jim Nasby | 2015-05-28 17:40:15 | Re: Fastest Backup & Restore for perf testing |