Message-ID: <7482c0a1ea0dba163e35160b4ee92ffb29052c2c.camel@cybertec.at>
Subject: Re: Partition table Creation and Testing using Inherited method
From: Laurenz Albe <laurenz.albe@cybertec.at>
To: dbatoCloud Solution <dbatocloud17@gmail.com>,
	pgsql-admin@lists.postgresql.org
Date: Wed, 03 Mar 2021 09:48:30 +0100
In-Reply-To: 
 <CAEz7P_s808_v372VzFvmf5vKN0Xp4F_cJRmMM9_6nvysgcEOGw@mail.gmail.com>
References: 
	<CAEz7P_s808_v372VzFvmf5vKN0Xp4F_cJRmMM9_6nvysgcEOGw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.5 (3.36.5-2.fc32) 
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Precedence: bulk

On Wed, 2021-03-03 at 08:49 +0530, dbatoCloud Solution wrote:
> Someone guide me on partitioning, I used the declarative method( inheritance),
>  Created child tables, added check constraints and steps below which I mentioned it.
> 
> step1 #
> CREATE TABLE core.contact_transaction_history (
> 
> record_insert_datetime timestamp NULL,
> crm_contact_type_id int4 NULL
> );
> 
> step2#
> CREATE TABLE core.contact_transaction_history_Year_2016() INHERITS (core.contact_transaction_history_PartMar2021);
> CREATE TABLE core.contact_transaction_history_Year_2017() INHERITS (core.contact_transaction_history_PartMar2021);
> CREATE TABLE core.contact_transaction_history_Year_2018() INHERITS (core.contact_transaction_history_PartMar2021);

Don't use inheritance partitioning.

Upgrade to a recent PostgreSQL release and use declarative partitioning.

It is so much better when it comes to performance and maintenance costs.

Yours,
Laurenz Albe
-- 
Cybertec | https://www.cybertec-postgresql.com