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 sh
On 5/27/15 3:39 PM, Steve Atkins wrote:
On May 27, 2015, at 1:24 PM, Wes Vaske (wvaske) wrote:
Hi,
I’m running performance tests against a PostgreSQL database (9.4) with various
hardware configurations and a couple different benchmarks (TPC-C & TPC-H).
I’m currently using pg_dump and pg_re
On Thu, May 28, 2015 at 10:31 AM, Ravi Krishna wrote:
> I am testing partitioning of a large table. I am doing a range
Sorry I forgot to clarify. I am using INHERITS for partioning with
check constraing built for range partitioning.
--
Sent via pgsql-performance mailing list (pgsql-performance
I am testing partitioning of a large table. I am doing a range
partitioning based on a sequence col, which also acts as the primary
key. For inserts I am using a trigger which will redirect insert to
the right table based on the value of the primary key.
Based on my testing, I see that the insert
