From: Jim Nasby <Jim.Nasby@BlueTreble.com>
To: Ravi Krishna <sravikrishna3@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: Partitioning and performance
Date: Thu, 28 May 2015 13:05:34 -0500
Message-ID: <556758EE.6000503@BlueTreble.com> (raw)
In-Reply-To: <CACER=P3NRTSiw-ivn5NcUGFXBEJHCK8kV6iv6cqw4c=kJNxEyg@mail.gmail.com>
References: <CACER=P3NRTSiw-ivn5NcUGFXBEJHCK8kV6iv6cqw4c=kJNxEyg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: Jim.Nasby@BlueTreble.com, sravikrishna3@gmail.com
Subject: Re: Partitioning and performance
In-Reply-To: <556758EE.6000503@BlueTreble.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox