Re: Partitioning and performance

From: Ravi Krishna <sravikrishna3(at)gmail(dot)com>
To: Melvin Davidson <melvin6925(at)gmail(dot)com>
Cc: Jan Lentfer <Jan(dot)Lentfer(at)web(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Partitioning and performance
Date: 2015-05-28 16:51:02
Message-ID: CACER=P30_XCxqQu35jCT+Vewy60exjhFhpH=iKPf1KvgxR9WEg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, May 28, 2015 at 12:42 PM, Melvin Davidson <melvin6925(at)gmail(dot)com> wrote:
>
> Generally, when you partition, data should only be in child tables, and the parent table should be empty, otherwise you defeat the purpose of parttioning.`

yes of course the parent table is empty. The trigger on insert is
redirecting it to the proper child table.

select count(*) from only tstesting.account ;
count
-------
0
(1 row)

select count(*) from only tstesting.account_part1 ;
count
-------
83659
(1 row)

select count(*) from only tstesting.account_part5 ;
count
-------
83659
(1 row)

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Ivann Ruiz 2015-05-28 16:56:29 WAL Streaming Failure PostgreSQL 9.4
Previous Message Tom Lane 2015-05-28 16:50:58 Re: Partitioning and performance