Subject: Re: Partitioning existing table issue - Help needed!
To: pgsql-admin@lists.postgresql.org
References: 
 <CAEz7P_v93GF4_irRugWvz7SrCNVHFEihEbuotaDJGu=WGyWbpQ@mail.gmail.com>
From: Thomas Kellerer <shammat@gmx.net>
Message-ID: <156bd5b9-d9aa-cfc2-d584-a8dd82acaf66@gmx.net>
Date: Fri, 5 Feb 2021 15:50:35 +0100
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.23)
 Gecko/20090812 Thunderbird/2.0.0.23 Mnenhy/0.7.6.666
MIME-Version: 1.0
In-Reply-To: 
 <CAEz7P_v93GF4_irRugWvz7SrCNVHFEihEbuotaDJGu=WGyWbpQ@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

dbatoCloud Solution schrieb am 04.02.2021 um 14:47:
> Dear All,
>
> I am partitioning the large table using declarative partitioning method =
in PostgreSQL 10.13.
>
>  1. created parent =C2=A0table
>  2. create sub-partitioned table
>  3. created index for each partition
>  4. created function
>  5. creating trigger but end with below error:-
>
> SQL Error [42809]: ERROR: "contact_transaction_history_parent_part_bkp_a=
m" is a partitioned table
>
> =C2=A0 Detail: Partitioned tables cannot have ROW triggers.

What do you need the trigger for?
And what does the trigger do?

If you insert into the parent table, Postgres will automatically store
the row in the appropriate partition.

Apart from the need to upgrade because row triggers on a partitioned table=
 require Postgres 11,
you might want to consider upgrading to at least Postgres 12 anyway, as th=
ere were
substantial partitioning improvements in 11 and 12 (performance and usabil=
ity wise)