From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
---|---|
To: | dbatoCloud Solution <dbatocloud17(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: Partition table Creation and Testing using Inherited method |
Date: | 2021-03-03 08:48:30 |
Message-ID: | 7482c0a1ea0dba163e35160b4ee92ffb29052c2c.camel@cybertec.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
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
From | Date | Subject | |
---|---|---|---|
Next Message | dbatoCloud Solution | 2021-03-03 09:01:07 | Re: Partition table Creation and Testing using Inherited method |
Previous Message | Laurenz Albe | 2021-03-03 08:46:42 | Re: Unix-domain sockets connections |